From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Mon, 25 May 2009 16:07:00 -0000 [thread overview]
Message-ID: <e394668d0905250907r1f978acbs57ad898d5f731189@mail.gmail.com> (raw)
In-Reply-To: <83zld1swbi.fsf@gnu.org>
On Sun, May 24, 2009 at 8:20 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> 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.
One thought I had was off/executable/on, [or whatever choices one prefers]
but I discounted it as not being acceptable.
If that's what y'all want, I'll resubmit another patch that does it that way.
next prev parent reply other threads:[~2009-05-25 16:07 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 [this message]
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=e394668d0905250907r1f978acbs57ad898d5f731189@mail.gmail.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--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