This is the mail archive of the gdb@sourceware.org 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] |
Hi Daniel, > > The problem that I have run into, is that I can find no way to let gdb know > > what dll's are inside the > > debugee using the remote protocol. > > > > Does anyone know if there is a way to do this ? > > There's no way to do this yet. If you look at the list archives for > the last several months, you'll see a patch (in the "GDB solib > interface" thread) that implements something which might help. But it > hasn't been finalized or committed yet (sorry Stephen - I just haven't > had time). 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? Mark, What do you think of this (untested) patch? We we couldn't find the function start address, the safest seems to be relying on ebp. -- Joel
Attachment:
i386-tdep.c.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |