Re: How to tell gdb about dlls using remote protocol

[Daniel Jacobowitz <drow@false.org>]

On Thu, Feb 01, 2007 at 03:03:01PM -0800, Joel Brobecker wrote:
> > 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.
> 
> At least on Windows, I think the change I proposed should help
> increase the odds in our favor in this situation. If I read the code
> correctly, the current approach will almost always fail, whereas
> using %ebp should get us somewhere sensible unless %ebp is used
> as a scratch register...

Except it's pretty standard to compile without a frame pointer on
Windows, from what I've encountered - and more importantly, all of the
Microsoft DLLs seem to do so.  I still think we need to come up with
some way to take advantage of the MS symbol info, though it's not a
small project (so I haven't really tried to do it).

-- 
Daniel Jacobowitz
CodeSourcery