Assertion fails in riched20; relay debug segfaults
ajharvey at myrealbox.com
Mon May 9 04:19:44 CDT 2005
On Sun, 2005-05-08 at 15:53 -0500, Dustin Navea wrote:
> Adrian Harvey wrote:
> > Thanks, Dustin, that sorts the riched problem. Any ideas as to why the
> > relay trace segfaults though? That was the bit I thought was
> > interesting... I have now found it will segfault even if wine is not
> > given an executable, so it's happening very early on.
> There are a couple of possible causes.
> 1) Are you using a 64-bit Linux, or 32, and if 64, are you compiling
> wine to 64-bit? It defaults (AFAIK) to 32, until you tell it otherwise..
I'm running the 64-bit version of Fedora core 3. Configure sets wine to
be compiled 32 bit on x86_64 systems, as Windows programs are all 32-bit
binaries and need a 32-bit ABI. It sets CC to gcc -m32 in the Makefile.
I guess when Windows64 bit has been out for a while, and stabilises, we
could look at how that handles 32->64 bit translation and work on a
similar method, but as no current apps depend on it it's a bit academic
at this stage.
configure is run as ./configure --x-libraries=/usr/X11R6/lib because
xmkmf, which configure uses to detect the x library location always
seems to return the lib64 directory, no matter how you try to force it
> 2) Im not sure (anyone else want to comment?), but I think relay was
> deprecated by +trace, but then again I could be wrong. If I am right
> about 2 though, then we should probably either at least fix relay so it
> doesnt segfault, or just remove it altogether.
I think Vincent answered this one...
More information about the wine-devel