From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Mon, 20 Jul 2009 13:21:00 -0000 [thread overview]
Message-ID: <200907201402.47393.pedro@codesourcery.com> (raw)
In-Reply-To: <e394668d0907101512q708b6bf3ua96e2ff55bdea4b9@mail.gmail.com>
[sorry for the delay, I'd been AFK]
On Friday 10 July 2009 23:12:19, Doug Evans wrote:
> The attached patch adds an optional regex argument to "info shared"
> and marks in the output libraries without debugging info.
> With this addition, I don't see a real need for a "set print
> symbol-loading-warning/whatever" option, thus I deleted it.
>
> Ok to check in?
>
I like this approach better. I like the regex consistency with
"sharedlibrary". I'm not sure if a '(*)' is the best UI, compared to
an explicit word, though, but I can live with it if others can too.
What do others think? Also, did you have a chance to run this
through your users?
Did you try this with any frontend? I've now realized that MI
clients are probably parsing "info sharedlibrary" output for
lack for an equivalent MI command. :-/ :-(
--
Pedro Alves
next prev parent reply other threads:[~2009-07-20 13:02 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
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 [this message]
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=200907201402.47393.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