From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Cc: Doug Evans <dje@google.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Thu, 04 Jun 2009 21:20:00 -0000 [thread overview]
Message-ID: <200906042221.22713.pedro@codesourcery.com> (raw)
In-Reply-To: <m3k53rwxez.fsf@fleche.redhat.com>
Sorry, I meant to reply earlier.
I also think that only giving the option of quieting symbol loadi
g from shared libraries libraries isn't desirable. Take the
below example. In this case, I'd like to have to option
of not printing the hundreds of "(no debugging symbols)" found
for executables (those are system executables, and I don't have
symbols for most of those).
(we clearly could do better with other kinds of messages below too)
>cd build/gdb
>make
>:
>touch ../../src/gdb/infrun.c
>./gdb -ex "set target-async 1" -ex "set non-stop 1" -ex "set schedule-multiple 1" -ex "set detach off" -ex "set pagination off" /usr/bin/make
GNU gdb (GDB) 6.8.50.20090603-cvs
:
(gdb) r&
Starting program: /usr/bin/make
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New process 15726]
[Thread debugging using libthread_db enabled]
process 15726 is executing new program: /bin/bash
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program exited normally.
[New process 15727]
[Thread debugging using libthread_db enabled]
process 15727 is executing new program: /bin/bash
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
process 15727 is executing new program: /usr/bin/make
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New process 15728]
[Thread debugging using libthread_db enabled]
process 15728 is executing new program: /bin/bash
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New process 15729]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New process 15730]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
process 15730 is executing new program: /usr/bin/make
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New process 15731]
[Thread debugging using libthread_db enabled]
process 15731 is executing new program: /bin/bash
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
process 15731 is executing new program: /usr/bin/make
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
Program exited normally.
Program exited normally.
Program exited normally.
Program exited normally.
Program exited normally.
[New process 15732]
[Thread debugging using libthread_db enabled]
process 15732 is executing new program: /bin/bash
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
process 15732 is executing new program: /usr/bin/gcc-4.2
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New process 15733]
process 15733 is executing new program: /usr/lib/gcc/x86_64-linux-gnu/4.2/cc1
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program exited normally.
[New process 15734]
process 15734 is executing new program: /usr/bin/as
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program exited normally.
Program exited normally.
[New process 15735]
[Thread debugging using libthread_db enabled]
process 15735 is executing new program: /bin/bash
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
process 15735 is executing new program: /bin/mv
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
:
:
:
process 16112 is executing new program: /usr/bin/make
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New process 16113]
[Thread debugging using libthread_db enabled]
process 16113 is executing new program: /bin/true
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program exited normally.
Program exited normally.
Program exited normally.
Program exited normally.
Program exited normally.
Program exited normally.
next prev parent reply other threads:[~2009-06-04 21: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
2009-05-25 16:07 ` Doug Evans
2009-06-04 20:34 ` Tom Tromey
2009-06-04 21:20 ` Pedro Alves [this message]
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=200906042221.22713.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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