Re: How to tell gdb about dlls using remote protocol

["Wiljan Derks" <Wiljan.Derks@zonnet.nl>]

I totoally agree with Joel that some practical approach is needed to make 
tracebacks
from code of which no information is available since usually most of the 
treads are somewhere
in a windows dll when stopping things.
The patch of Joel is based on a procedure that checks if code is in a known 
dll.
This is exactly what got me into problems when trying to make tracebacks 
using the gdb remote
interface on windows.
Because the gdb remote protocol does not allow to inform gdb about the dll's 
in de debugee,
this patch does not work in that case.
For that reason, I modified the code so that I check if the pc is inside one 
of the sections of the program.
If it is not, I use the same unwinding as used in Joels patch when the pc is 
detected to be in some dll.
This avoids having knowledge about the dlls in gdb and still gives the same 
tracebacks.
I guess the result is the same as for Joels patch, except that now also the 
remote protocol works
because gdb does not need to have knowledge on the dlls.

This patch made things work for me using the remote protocol of gdb.

What do you think of this approach ?

Wiljan