Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@redhat.com>,
	gdb-patches <gdb-patches@sourceware.org>,
	        Pedro Alves <pedro@codesourcery.com>
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Tue, 30 Jun 2009 21:49:00 -0000	[thread overview]
Message-ID: <e394668d0906301449n24a083cfo186bd10dd5280c@mail.gmail.com> (raw)
In-Reply-To: <200906222035.48910.pedro@codesourcery.com>

On Mon, Jun 22, 2009 at 12:35 PM, Pedro Alves<pedro@codesourcery.com> wrote:
> On Monday 22 June 2009 18:52:40, Tom Tromey wrote:
> I like gdb's output with
> Doug's suggestion.

So we have two yeas and zero nays.

Eli, are the docs ok?
Copied below.

Here's the original email:
http://sourceware.org/ml/gdb-patches/2009-06/msg00495.html


Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.313
diff -u -p -r1.313 NEWS
--- NEWS	11 Jun 2009 11:57:46 -0000	1.313
+++ NEWS	18 Jun 2009 23:59:23 -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 symbol-loading-warnings
+show print symbol-loading-warnings
+  Control printing of warnings when auto-loading files without
+  debugging symbols.

 set debug timestamp
 show debug timestamp


Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.600
diff -u -p -r1.600 gdb.texinfo
--- doc/gdb.texinfo	15 Jun 2009 12:11:36 -0000	1.600
+++ doc/gdb.texinfo	18 Jun 2009 23:59:24 -0000
@@ -12480,21 +12480,21 @@ is printed as follows:
 @item show opaque-type-resolution
 Show whether opaque types are resolved or not.

-@kindex set print symbol-loading
-@cindex print messages when symbols are loaded
-@item set print symbol-loading
-@itemx set print symbol-loading on
-@itemx set print symbol-loading off
-The @code{set print symbol-loading} command allows you to enable or
-disable printing of messages when @value{GDBN} loads symbols.
-By default, these messages will be printed, and normally this is what
-you want.  Disabling these messages is useful when debugging applications
-with lots of shared libraries where the quantity of output can be more
-annoying than useful.
+@kindex set print symbol-loading-warnings
+@cindex print warnings when auto-loading files without symbols
+@item set print symbol-loading-warnings
+@itemx set print symbol-loading-warnings on
+@itemx set print symbol-loading-warnings off
+The @code{set print symbol-loading-warnings} command allows you to enable or
+disable printing of warning messages when @value{GDBN} implicitly loads symbols
+for files.  By default, these messages are disabled.
+When debugging applications with lots of shared libraries the quantity
+of output can be more annoying than useful.

-@kindex show print symbol-loading
+@kindex show print symbol-loading-warnings
 @item show print symbol-loading
-Show whether messages will be printed when @value{GDBN} loads symbols.
+Show whether warnings will be printed when @value{GDBN} implicitly loads
+symbols for files.

 @kindex maint print symbols
 @cindex symbol dump


  reply	other threads:[~2009-06-30 21:49 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
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 [this message]
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=e394668d0906301449n24a083cfo186bd10dd5280c@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=tromey@redhat.com \
    /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