how do I find where wine itself is segfaulting?
Background. I am trying to figure out why a program that I thought ran OK on 25 October no longer runs and no longer runs when I recompile from that code too. So the program accesses invalid memory down inside the WNDPROC stuff (winproc.c line 418, it says, so I guess it means line 416) So I turn on WINDEBUG=+relay to see what is being passed. And wine segfaults. Even export WINEDEBUG=+relay wine --version which yields 0009:Call kernel32.__wine_kernel_init() ret=77ed4e4d Segmentation fault I can't use gdb and I can't use winedbg. Anyone know what is going on? -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed
Hi, I'm running into the same problem. File on the resulting core tells me it was generated from wine-preloader. I'm using wine 0.9.2 for Fedora Core 3 from winehq (the i686 version I believe). I'm running an x86_64, if that matters. -- Keith --- Bill Medland <billmedland(a)mercuryspeed.com> wrote:
Background. I am trying to figure out why a program that I thought ran OK on 25 October no longer runs and no longer runs when I recompile from that code too.
So the program accesses invalid memory down inside the WNDPROC stuff (winproc.c line 418, it says, so I guess it means line 416)
So I turn on WINDEBUG=+relay to see what is being passed.
And wine segfaults.
Even export WINEDEBUG=+relay wine --version
which yields 0009:Call kernel32.__wine_kernel_init() ret=77ed4e4d Segmentation fault
I can't use gdb and I can't use winedbg.
Anyone know what is going on?
-- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
--- Bill Medland <billmedland(a)mercuryspeed.com> wrote:
So I turn on WINDEBUG=+relay to see what is being passed.
And wine segfaults.
Anyone know what is going on?
On Wed, 7 Dec 2005, Keith Dunwoody wrote:
I'm running into the same problem. File on the resulting core tells me it was generated from wine-preloader. I'm using wine 0.9.2 for Fedora Core 3 from winehq (the i686 version I believe). I'm running an x86_64, if that matters.
You are not the first: http://www.winehq.org/pipermail/wine-devel/2005-November/041988.html http://www.winehq.org/hypermail/wine-devel/2005/03/0636.html http://www.winehq.com/hypermail/wine-devel/2005/05/0328.html Wine crashes the first time it enters/uses a entry/function using the debug setup from ntdll/relay.c:RELAY_SetupDLL. (Which happens to be a RtlInitUnicode in kernel/module:GetModuleHandleW) . If you exclude the ntdll in relaying, wine - without parameters - does not crash. BUT at soon as you try running a program it will cracsh when calling a kernel32/* function. I get something like: Unhandled exception: page fault on read access to 0x7fd58bdc in 32-bit code (0x7fd58bdc). In 32 bit mode. Register dump: CS:0073 SS:007b DS:007b ES:007b FS:1007 GS:0033 EIP:7fd58bdc ESP:7fc6fd30 EBP:7fc6fd3c EFLAGS:00010246( - 00 -RIZP1) EAX:7f9b8809 EBX:7f9d51c8 ECX:00000001 EDX:7f9b0000 ESI:00000001 EDI:00000001 Stack dump: 0x7fc6fd30: 7f9cfb4b 7f9b0000 7f9d51c8 7fc6fd5c 0x7fc6fd40: 7f9cfab8 7f9b0000 00000001 00000001 0x7fc6fd50: 7bef15d4 00000009 7f9cfa90 7fc6fd74 0x7fc6fd60: 7bebf692 7f9b0000 00000001 00000001 0x7fc6fd70: 7bef15d4 7fc6fe00 7bec03aa 7f9cfa90 0x7fc6fd80: 7f9b0000 00000001 00000001 7fc6fda0 0200: sel=1007 base=7fee2000 limit=00001fff 32-bit rw- Backtrace: =>1 0x7fd58bdc in kernel32 (+0x88bdc) (0x7fc6fd3c) Peter
On December 8, 2005 03:08 am, Peter Berg Larsen wrote:
--- Bill Medland <billmedland(a)mercuryspeed.com> wrote:
So I turn on WINDEBUG=+relay to see what is being passed.
And wine segfaults.
Anyone know what is going on?
On Wed, 7 Dec 2005, Keith Dunwoody wrote:
I'm running into the same problem. File on the resulting core tells me it was generated from wine-preloader. I'm using wine 0.9.2 for Fedora Core 3 from winehq (the i686 version I believe). I'm running an x86_64, if that matters.
You are not the first:
http://www.winehq.org/pipermail/wine-devel/2005-November/04198 8.html
http://www.winehq.org/hypermail/wine-devel/2005/03/0636.html
http://www.winehq.com/hypermail/wine-devel/2005/05/0328.html
Wine crashes the first time it enters/uses a entry/function using the debug setup from ntdll/relay.c:RELAY_SetupDLL. (Which happens to be a RtlInitUnicode in kernel/module:GetModuleHandleW) .
So is anyone actively looking into this? I'll make a start until someone says that they are already doing it.
Peter
Bill Medland wrote:
Wine crashes the first time it enters/uses a entry/function using the debug setup from ntdll/relay.c:RELAY_SetupDLL. (Which happens to be a RtlInitUnicode in kernel/module:GetModuleHandleW) .
So is anyone actively looking into this? I'll make a start until someone says that they are already doing it.
We have a hack in CrossOver's Wine to avoid crashes in +relay. This might help you see what's happening after the point of the crash in Wine. See the attached patch. Mike Index: dlls/ntdll/relay.c =================================================================== RCS file: /cvstrees/crossover/office/wine/dlls/ntdll/relay.c,v retrieving revision 1.1.1.19 retrieving revision 1.22 diff -u -r1.1.1.19 -r1.22 --- dlls/ntdll/relay.c 30 Nov 2005 13:23:56 -0000 1.1.1.19 +++ dlls/ntdll/relay.c 30 Nov 2005 14:52:06 -0000 1.22 @@ -847,6 +847,7 @@ int i,nostring; DPRINTF("%08lx",x); + return; if (!HIWORD(x) || TRACE_ON(seh)) return; /* trivial reject to avoid faults */ __TRY {
On December 8, 2005 09:40 am, Mike McCormack wrote:
Bill Medland wrote:
Wine crashes the first time it enters/uses a entry/function using the debug setup from ntdll/relay.c:RELAY_SetupDLL. (Which happens to be a RtlInitUnicode in kernel/module:GetModuleHandleW) .
So is anyone actively looking into this? I'll make a start until someone says that they are already doing it.
We have a hack in CrossOver's Wine to avoid crashes in +relay. This might help you see what's happening after the point of the crash in Wine. See the attached patch.
Mike Actually that doesn't help in my case. -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed
On December 8, 2005 09:15 am, Bill Medland wrote:
On December 8, 2005 03:08 am, Peter Berg Larsen wrote:
--- Bill Medland <billmedland(a)mercuryspeed.com> wrote:
So I turn on WINDEBUG=+relay to see what is being passed.
And wine segfaults.
Anyone know what is going on?
On Wed, 7 Dec 2005, Keith Dunwoody wrote:
I'm running into the same problem. File on the resulting core tells me it was generated from wine-preloader. I'm using wine 0.9.2 for Fedora Core 3 from winehq (the i686 version I believe). I'm running an x86_64, if that matters.
You are not the first:
http://www.winehq.org/pipermail/wine-devel/2005-November/041 98 8.html
http://www.winehq.org/hypermail/wine-devel/2005/03/0636.html
http://www.winehq.com/hypermail/wine-devel/2005/05/0328.html
Wine crashes the first time it enters/uses a entry/function using the debug setup from ntdll/relay.c:RELAY_SetupDLL. (Which happens to be a RtlInitUnicode in kernel/module:GetModuleHandleW) .
So is anyone actively looking into this? I'll make a start until someone says that they are already doing it.
Peter So it is looking to me as if it (and my original problem) is something to do with the cpu or memory. It used to work on my Celeron with 512MB but it doesn't work on my brand new Dell Optiplex GX280 with 1GB. (I am currently working to remove any other differences).
Does that make any sense to anyone? -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed
On December 8, 2005 02:40 pm, Bill Medland wrote:
On December 8, 2005 09:15 am, Bill Medland wrote:
On December 8, 2005 03:08 am, Peter Berg Larsen wrote:
--- Bill Medland <billmedland(a)mercuryspeed.com> wrote:
So I turn on WINDEBUG=+relay to see what is being passed.
And wine segfaults.
Anyone know what is going on?
On Wed, 7 Dec 2005, Keith Dunwoody wrote:
I'm running into the same problem. File on the resulting core tells me it was generated from wine-preloader. I'm using wine 0.9.2 for Fedora Core 3 from winehq (the i686 version I believe). I'm running an x86_64, if that matters.
You are not the first:
http://www.winehq.org/pipermail/wine-devel/2005-November/0 41 98 8.html
http://www.winehq.org/hypermail/wine-devel/2005/03/0636.ht ml
http://www.winehq.com/hypermail/wine-devel/2005/05/0328.ht ml
Wine crashes the first time it enters/uses a entry/function using the debug setup from ntdll/relay.c:RELAY_SetupDLL. (Which happens to be a RtlInitUnicode in kernel/module:GetModuleHandleW) .
So is anyone actively looking into this? I'll make a start until someone says that they are already doing it.
Peter
So it is looking to me as if it (and my original problem) is something to do with the cpu or memory. It used to work on my Celeron with 512MB but it doesn't work on my brand new Dell Optiplex GX280 with 1GB. (I am currently working to remove any other differences).
Does that make any sense to anyone? Wrong. It's the kernel choice. It works on the non-smp kernel and fails on the smp kernel. (2.6.9-22.EL works; 2.6.9-22.ELsmp fails, both are RedHat kernels)
-- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed
On Thu, 8 Dec 2005, Bill Medland wrote:
Wrong. It's the kernel choice. It works on the non-smp kernel and fails on the smp kernel. (2.6.9-22.EL works; 2.6.9-22.ELsmp fails, both are RedHat kernels)
Try booting with noexec=off. I tried that when I asked wine-devel a month ago, but my mandrake crashed - for some obscure reasons - before reaching a prompt. Peter
participants (4)
-
Bill Medland -
Keith Dunwoody -
Mike McCormack -
Peter Berg Larsen