This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [6.2] PROBLEMS file


> Date: Thu, 22 Jul 2004 08:17:01 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> 
> We saw the same sort of issues on Windows as well, trying to unwind
> from functions in the ntdll DLL. Unfortunately in that case, we don't
> get an infinite backtrace, we get a backtrace that doesn't provide
> the part that the user is probably looking for (the part refering to
> his code, before the call to the ntdll services). Something like this:
> 
>     #0  0x7ffe0304 in ?? ()
>     #1  0x77f7f4af in ntdll!ZwWaitForSingleObject () from ntdll.dll
>     #2  0x77e7788b in WaitForSingleObjectEx () from /WINDOWS/system32/KERNEL32.DLL
>     #3  0x00000778 in ?? ()
>     #4  0x00000000 in ?? () from 
>     #5  0x010df2c8 in ?? ()
>     #6  0x000003e8 in ?? ()
>     [snip]
>     #27 0x77e79d6a in WaitForSingleObject () from /WINDOWS/system32/KERNEL32.DLL
>     #28 0x00000778 in ?? ()
>     #29 0x000003e8 in ?? ()
>     #30 0x00000000 in ?? () from 
>     #31 0x61074971 in siginterrupt () from /bin/cygwin1.dll
>     Previous frame inner to this frame (corrupt stack?)
> 
> In the backtrace above, only frame 0 to 2 are correct. After that,
> GDB goes in limbo until it finally finds out that something is wrong.

That is exactly what I saw with the DJGPP port.  Was the program in
your case compiled with DWARF2 debug info or with some other format?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]