This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: How to tell gdb about dlls using remote protocol
- From: Daniel Jacobowitz <drow at false dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Wiljan Derks <Wiljan dot Derks at zonnet dot nl>, gdb at sourceware dot org, Mark Kettenis <kettenis at gnu dot org>
- Date: Thu, 1 Feb 2007 17:54:37 -0500
- Subject: Re: How to tell gdb about dlls using remote protocol
- References: <003f01c7457c$0f2d8090$9600000a@kamer> <20070131223113.GA15122@nevyn.them.org> <20070201175311.GG17864@adacore.com>
On Thu, Feb 01, 2007 at 09:53:11AM -0800, Joel Brobecker wrote:
> This makes me wonder how well the debugger can work in certain
> situations like when backtracing from DLL code. If the debugger
> doesn't know where it is, then it's probably let to prologue analysis
> to do the unwinding. Except that it cannot determine where the prologue
> is... In that case, I see that the i386 unwinder assumes that the frame
> base can be deduced from the SP and the SP offset. Unfortunately,
> this SP offset can only be deduced from prologue analysis. Catch 22?
In general, if we can not find the start of the current function,
we have absolutely no chance of getting out of it.
This is a standard problem e.g. with the Windows system DLLs, since
we have inadequate means to recover symbol information from them.
--
Daniel Jacobowitz
CodeSourcery