Re: GDB Incorrectly Reads & Resolves Shared Library Symbols [MinGW-w64]

[William Adair <will.adair01@gmail.com>]

Hannes,

Unfortunately, I do not. It appears I'm left with little choice but to
debug GDB itself while it's debugging the executable that loads the shared
library. I'll add that I am using a custom linker command file and that may
be ruining some predefined expectation from GDB on what data should be in
certain sections, but I haven't dug far enough into GDB source to figure
out how it loads symbols from the binary image, yet.

On Sun, Nov 1, 2020 at 9:53 AM Hannes Domani <ssbssa@yahoo.de> wrote:

>  Am Sonntag, 1. November 2020, 00:26:34 MEZ hat William Adair via Gdb <
> gdb@sourceware.org> Folgendes geschrieben:
>
> > Can anyone recommend a way to start debugging GDB? I've found that when I
> > compile a 32-bit shared library that GDB is unable to correctly resolve
> the
> > symbols in the image and set breakpoints. Even when I reach a segfault
> and
> > print the backtrace, the symbols are incorrect or flat out missing. I
> > already verified that the image has .debug_* sections as would be
> required
> > for DWARF debugging, so I'm perplexed as to why GDB cannot correctly
> > resolve it and am looking for guidance.
> >
> > Thank you.
>
> Do you have a (small) example where this problem can be reproduced?
>
>
> Hannes
>