how do I find where wine itself is segfaulting?

[Peter Berg Larsen]

> --- Bill Medland <billmedland at 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