Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Mon, 25 May 2009 03:20:00 -0000	[thread overview]
Message-ID: <83zld1swbi.fsf@gnu.org> (raw)
In-Reply-To: <20090523232414.BED2B846C2@localhost>

> Date: Sat, 23 May 2009 16:24:14 -0700 (PDT)
> From: dje@google.com (Doug Evans)
> 
> We'd like to avoid adding any new option.
> And I'd like to avoid ports having to specify what system libraries are.
> That may be ultimately useful, but it seems excessive for the task at hand.
> OTOH, "set print symbol-loading off|on" is new for 7.0, so we could
> replace it with something else if that's TRTTD.
> 
> The high-order bit of what needs to be done here is to be able
> to turn off the warnings for shared-libs.  And since
> "set print symbol-loading off|on" is new for 7.0 ...
> 
> I propose the following:
> 
> 1) rename "set print symbol-loading" to "set print solib-symbol-loading"
> 2) always print such messages for the main executable

There's also a possibility to make this a tristate option instead of a
simple boolean one.  After all, it's quite possible that development
snapshots of GDB were available on several GNU/Linux distros for some
time, and so the argument of "new in GDB 7.0" is not necessarily
strong enough.

> --- NEWS	18 May 2009 13:25:33 -0000	1.312
> +++ NEWS	23 May 2009 22:36:12 -0000
> @@ -193,9 +193,10 @@ set sh calling-convention
>  show sh calling-convention
>    Control the calling convention used when calling SH target functions.
>  
> -set print symbol-loading
> -show print symbol-loading
> -  Control printing of symbol loading messages.
> +set print solib-symbol-loading
> +show print solib-symbol-loading
> +  Control printing of messages when loading symbols from shared object
> +  libraries.

This is okay.

> @@ -4175,9 +4197,9 @@ the global debug-file directory prepende
>  				     &setlist, &showlist);
>  
>    add_setshow_boolean_cmd ("symbol-loading", no_class,
> -                           &print_symbol_loading, _("\
> -Set printing of symbol loading messages."), _("\
> -Show printing of symbol loading messages."), NULL,
> +                           &print_solib_symbol_loading, _("\
> +Set printing of symbol loading messages for shared object libraries."), _("\
> +Show printing of symbol loading messages for shared object libraries."), NULL,

This seem to leave the option's name unaltered, unlike your
explanations and unlike the docs changes.  Or am I missing something?

> --- doc/gdb.texinfo	15 May 2009 16:53:45 -0000	1.593
> +++ doc/gdb.texinfo	23 May 2009 22:36:13 -0000

This part is approved, assuming we agree to the code change and the
removal of the previous functionality,. and also subject to a couple
of comments:

> +@cindex print messages when shared object library symbols are loaded

This index entry is too long.  Suggest to shorten it like this:

  @cindex announce loading symbols from shared libraries

I would also add another one:

  @cindex shared libraries, announce loading symbols

> +The @code{set print solib-symbol-loading} command allows you to enable or

"This command" is shorter and doesn't lose any information, since the
name of the command is clearly visible at this spot.

Thanks.


  reply	other threads:[~2009-05-25  3:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23 23:24 Doug Evans
2009-05-25  3:20 ` Eli Zaretskii [this message]
2009-05-25 16:07   ` Doug Evans
2009-06-04 20:34     ` Tom Tromey
2009-06-04 21:20       ` Pedro Alves
2009-06-05 18:19         ` Tom Tromey
2009-06-05 18:49           ` Pedro Alves
2009-06-05 22:18             ` Tom Tromey
2009-06-19  0:48               ` Doug Evans
2009-06-22 17:54                 ` Tom Tromey
2009-06-22 19:35                   ` Pedro Alves
2009-06-30 21:49                     ` Doug Evans
2009-06-30 21:55                       ` Pedro Alves
2009-06-30 22:20                         ` Doug Evans
2009-07-01  2:29                           ` Tom Tromey
2009-07-01  3:13                       ` Eli Zaretskii
2009-07-01  3:47                         ` Doug Evans
2009-07-01 17:48                           ` Eli Zaretskii
2009-07-01 17:53                             ` Doug Evans
2009-07-01 18:01                               ` Pedro Alves
2009-07-01 19:55                                 ` Doug Evans
2009-07-02 13:26                                   ` Pedro Alves
2009-07-02 20:08                                     ` Doug Evans
2009-07-02 22:43                                       ` Pedro Alves
2009-07-11  4:22                                         ` Doug Evans
2009-07-20 13:21                                           ` Pedro Alves
2009-07-23 18:57                                             ` Doug Evans
2009-07-27 17:15                                               ` Tom Tromey
2009-08-24 22:02                                                 ` Doug Evans
2009-08-25  3:47                                                   ` Eli Zaretskii
2009-08-27 19:11                                                   ` Tom Tromey
2009-08-27 23:39                                                     ` Doug Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zld1swbi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox