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

["Mark Kettenis" <mark.kettenis@xs4all.nl>]

>  On Mon, Nov 10, 2008 at 8:19 PM, Daniel Jacobowitz <drow@false.org> wrote:
> > On Tue, Nov 11, 2008 at 06:10:46AM +0200, Eli Zaretskii wrote:
> >> I thought the original patch came with a suggestion to add an option,
> >> in case user wanted to see these messages.
> >
> > OK, I understand now.  I'd be fine with the shared library messages
> > disabled or made consistent under 'set verbose'.  I don't think adding
> > a new option would be great.
>
>  How about this?
>
>  I changed the calls to have_{partial,full}_symbols to two new
>  functions objfile_has_{partial,full}_symbols.  I think it's TRTTD
>  here.
>  This patch also adds a test for info_verbose so the messages are
>  printed for shared libs if verbosity turned on.

Sorry I'm a bit late in this discussion, but I do really like the messages
about missing symbol info for shared libraries.  To me they provide an
important hint that my debugging session is likely to run into problems at
some point. My perspective may be a bit different since I use an operating
system that ships all of its core libraries with full debug info. But we
really shouldn't consider proprietary operating systems as the norm here,
and we should encourage other Open Source systems to ship their libraries
with debug info.

>  2008-11-20  Doug Evans  <dje@google.com>
>
>          * objfiles.h (objfile_has_partial_symbols): Declare.
>          (objfile_has_full_symbols): Declare.
>          * objfiles.c (objfile_has_partial_symbols): New function.
>          (objfile_has_full_symbols): New function.
>          * symfile.c (symbol_file_add_with_addrs_or_offsets): Only print
>          "no debugging symbols found" for main program, unless the user
>          turns on verbosity.
>