What the HELL is deadbeef?! Or lstat64.c?

[Praedor Tempus]

lawson_whitney at juno.com wrote:
I didn't get any fixme's.  What I did get was a long list of "No debug 
information in 32bit DLL '<list of windoze dlls>' (0x.....)" and a long 
list of "No debug information in ELF '/usr/X11R6/<many libs>... and 
'/usr/lib/wine/<many wine *.so files>' ... and '/lib/<number of system 
libs>'...

Scrolling up through the debug window shows no fixme's.  It then ends as I 
described with the deadbeef reference and, now, I do NOT get a request for 
the path to lstat64.c.  That appears to have been a one-time deal the first 
time I attempted to run IE 6.0 (I got the same sort of response, by the 
way, when trying to run the previous version on my system IE 5.0 - but it 
was with a stripped wine version so I didn't get the debug window).

> On Tue, 25 Sep 2001, Praedor Tempus wrote:
> 
>> Wow, fast responses.  Thanks.
>>
>> OK, deadbeef is a deadend.
> 
> Not necessarily.  0xdeadbeef is the address of Wine's handler for
> unknown functions, such as foo.dll ordinal 2227.  Did you not get some
> fixme's before from fixup-imports?  When a native dll tries to import a
> function Wine knows nothing about, not even enough to make a stub for
> it, it sets the handler address to 0xdeadbeef.  Okay, it is an
>