>
> Please open a bug and discuss this problem via bugzilla, rather than on
> wine-devel.
>
OK. Bug #6622 has been registered. Let's move our efforts to bugzilla.
Regards, Pavel
Pavel Troller wrote:
It is usuyally generated from wine-pthread
gdb wine-pthread core.19668
Please open a bug and discuss this problem via bugzilla, rather than on
wine-devel.
Mike
Hi!
> It is usuyally generated from wine-pthread
>
> gdb wine-pthread core.19668
> bt
It showed the following:
[EMAIL PROTECTED]:~$ gdb wine-pthread core.19668
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
On Tue, Nov 07, 2006 at 06:44:31AM +0100, Pavel Troller wrote:
> >
> > We just have to find out _why_ it breaks. Should not be too hard
> > with some backtraces or similar.
> >
> Hi!
> Today I tried to generate a backtrace. However, I simply failed.
> I've recompiled wine with full debug, and
>
> We just have to find out _why_ it breaks. Should not be too hard
> with some backtraces or similar.
>
Hi!
Today I tried to generate a backtrace. However, I simply failed.
I've recompiled wine with full debug, and reinstalled. Then I
installed the newest gdb (6.5), because my older one (6.
> I am using a 2.6.18 based openSUSE 10.2 Beta1 kernel and Wine works fine
> there. (AMD64 however).
Your NoExec protection is on or off?
And question to all: is there someone with new (2.6.18.x) vanilla
kernel
(downloaded from kernel.org), noexec=on and perfectly working Wine?
> I saw a few others say that this worked around the problem, so I
> rebooted and added noexec=off ... I still get the segfault running
> wine from make.
Unfortunatelly I cannot reproduce your problem. Under 2.6.18.1 with
noexec=off simple Makefile posted by Jimmy W works fine for me. So
Then probably the only way to unbreak the broken apps is to add noexec=off
to the kernel command line.
I saw a few others say that this worked around the problem, so I
rebooted and added noexec=off ... I still get the segfault running
wine from make.
On Mon, Nov 06, 2006 at 04:40:48PM +0100, Pavel Troller wrote:
> >
> > this is what i did - and also suggest quite some time ago him(?)/list. i
> > had the same problem since .16 kernels (unstable(~) gentoo-source
> > ebuild). since that change everything works fine (.18 now).
> >
> Hi!
> Yes,
>
> this is what i did - and also suggest quite some time ago him(?)/list. i
> had the same problem since .16 kernels (unstable(~) gentoo-source
> ebuild). since that change everything works fine (.18 now).
>
Hi!
Yes, you did, and you did correctly. I just rebooted the x86_64 machine
with noex
On Mon, Nov 06, 2006 at 10:29:22PM +0800, Dmitry Timoshkov wrote:
> > 3) I'm using exec-shield patch, but I can disable it (for sure,
> > tested by the pax testing suite) using a procfs entry. Even with
> > exec-shield disabled the crash is still there, and in 2.6.17, even
> > with exec-shield ena
"Pavel Troller" <[EMAIL PROTECTED]> wrote:
>fixme:seh:check_no_exec No-exec fault triggered at 0x401000, enabling
>work-around
Are you using SeLinux or some other patches? If so, please try building
your kernel from the vanilla Linux kernel.org sources.
Hi Mike!
I take you very seriously
>
> >fixme:seh:check_no_exec No-exec fault triggered at 0x401000, enabling
> >work-around
>
> Are you using SeLinux or some other patches? If so, please try building
> your kernel from the vanilla Linux kernel.org sources.
>
Hi Mike!
I take you very seriously, I know that you are a real win
L. Rahyen wrote:
fixme:seh:check_no_exec No-exec fault triggered at 0x401000, enabling
work-around
Are you using SeLinux or some other patches? If so, please try building
your kernel from the vanilla Linux kernel.org sources.
Mike
On Mon, Nov 06, 2006 at 08:46:40AM +0100, Pavel Troller wrote:
> > This seems to be Wine-related problem (but not neccessary Wine bug)
> > because
> > everything else works fine with 2.6.18.1 kernel; I'm not alone who have
> > strange problems with Wine under 2.6.18 kernel.
>
> No, you ar
> This seems to be Wine-related problem (but not neccessary Wine bug)
> because
> everything else works fine with 2.6.18.1 kernel; I'm not alone who have
> strange problems with Wine under 2.6.18 kernel.
No, you are not. I've posted a very similar problem with wine & 2.6.18
a couple of
> ...with same configuration under 2.6.18.1 kernel Wine doesn't work.
> ...
> I have errors like these ones when I try to launch something with Wine:
>
> fixme:seh:check_no_exec No-exec fault triggered at 0x401000, enabling
> work-around fixme:seh:check_no_exec No-exec fault triggered at 0x4
> > I recently tried 2.6.18.1 kernel and wine stoped working. Then I
> > downgraded to 2.6.16.18 and wine working fine now.
>
> I'm using a custom built 2.6.18.1 on Debian Unstable/AMD64 now, and Wine
> works fine for me, so this is unlikely to be a Wine problem.
I compiled 2.6.18.1 wi
L. Rahyen wrote:
The system is gentoo linux (2.6.18-gentoo-r1)
I recently tried 2.6.18.1 kernel and wine stoped working. Then I downgraded
to 2.6.16.18 and wine working fine now.
I'm using a custom built 2.6.18.1 on Debian Unstable/AMD64 now, and Wine
works fine for me, so this is unlikel
> The system is gentoo linux (2.6.18-gentoo-r1)
I recently tried 2.6.18.1 kernel and wine stoped working. Then I
downgraded
to 2.6.16.18 and wine working fine now.
After doing some important work, I will recompile 2.6.18.1 again with
same .config and will see what happens. But b
# wine --version
Works!
But:
Makefile
-
test:
wine --version
-
Then run:
#make test
Wine will segfault!
I am having the same problem.
I use wine to run a compiler from a Makefile. A few months ago,
it worked fine, but recently it stopped working. I even downgraded
to
On Mon, Oct 30, 2006 at 08:36:48AM +0100, Jimmy W wrote:
> It says that wine is compiled with the:
>
> ./configure CFLAGS=-fno-stack-protector
>
> So the bug shud not apply, also i have been installing binaries for
> other distribution (debian binaries) also from winehq own ubuntu rep.
>
> I th
It says that wine is compiled with the:
./configure CFLAGS=-fno-stack-protector
So the bug shud not apply, also i have been installing binaries for
other distribution (debian binaries) also from winehq own ubuntu rep.
I think the problem is deeper in wine.
/Jimmy
sön 2006-10-29 klockan 13:09
On 10/29/06, Jimmy W <[EMAIL PROTECTED]> wrote:
I got a simple problem, that got really hard to fix.
I am trying to cross-compile stuff over a Makefile with ms compiler.
Problem is that when make are executing wine as a command, wine
segfaults.
An example:
# wine --version
Works!
But:
Mak
I got a simple problem, that got really hard to fix.
I am trying to cross-compile stuff over a Makefile with ms compiler.
Problem is that when make are executing wine as a command, wine
segfaults.
An example:
# wine --version
Works!
But:
Makefile
-
test:
wine --version
--
25 matches
Mail list logo
