gdb stack trace problems (Addendum)

[Mark Kettenis]

Hi Roland,

[Dropped Dan, he's busy enough with other stuff, and he can always read it
on the list]

> Also I want to mention that it might have something to do with threading.
> In a nonthreaded app I don't have any problems with gdb 6.3.50 stack
> dumping.

Only if it links in different code, or is multi-threading still cooperative
on Windblows.  Anyway, what I really need is the disassembly for SleepEx as
implemented in the DLL.  Not the import stub, or dissassembly of some random
memory contents (the Sleep you showd is an import stub, and the call
*0xdeadbeef in it means it calls the contents of address 0xdeadbeef, not
address 0xdeadbeef itself).

Cheers,

Mark