Re: too many "no debugging symbols found" messages from shared libs

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 21 Nov 2008 14:53:39 -0800
> From: Doug Evans <dje@google.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, brobecker@adacore.com,
>         gdb-patches@sourceware.org
> 
> The outstanding question is:  When debugging executables with symbols,
> do we want to start printing "no debugging symbols found" messages for
> every such shared library encountered as the default behavior?  If
> yes, it can still be turned off with "set print symbol-loading off".
> If no, then the user would have to turn on some other option in order
> to see them ("set verbose on" is the current proposal).
> 
> Comments?

I agree that the current logic has its flaws, but I think I understand
the difficulty: the problem is with shared libraries that are part of
the program you are debugging vs system libraries, like libc.so.  We
probably do NOT want to hear about stripped system libraries by
default, but we do want those messages for libraries that are part of
the application, if the application isn't stripped.

Can we find a good way of supporting both these use cases?