From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
mark.kettenis@xs4all.nl, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: too many "no debugging symbols found" messages from shared libs
Date: Mon, 24 Nov 2008 19:42:00 -0000 [thread overview]
Message-ID: <e394668d0811240819o2b7da132xe8150c9cc8e97c4c@mail.gmail.com> (raw)
In-Reply-To: <ufxlhix1t.fsf@gnu.org>
On Sun, Nov 23, 2008 at 8:10 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 22 Nov 2008 11:07:48 -0800
>> From: Paul Pluzhnikov <ppluzhnikov@google.com>
>> Cc: Doug Evans <dje@google.com>, mark.kettenis@xs4all.nl, brobecker@adacore.com, gdb-patches@sourceware.org
>>
>> On Sat, Nov 22, 2008 at 3:58 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> > Can we find a good way of supporting both these use cases?
>>
>> Any library under /lib{,64}, /usr/lib{,64} and /usr/local/lib{,64}
>> is likely not an "application in development" library (although
>> there are obvious exceptions to this heuristic).
>>
>> Another alternative: allow the user to "silence" specific
>> libraries via a glob pattern, e.g.
>>
>> set system-library "/lib*/libc.so.6 /lib*/libpthread.so.1"
>>
>> The default could be "/lib* /usr/lib* /usr/local/lib*", which
>> would be equivalent to the heuristic above. A user who cares
>> about all libraries could reset this to "". A user who
>> doesn't care about any could set this to "*".
>
> I'd prefer the latter method.
>
>> [Use ';' instead of space to separate patterns on *win* targets.]
>
> Yes, and Windows needs a different default for the system libraries.
There's nothing in 'set system-library foo' that says it's for
suppressing "no debugging symbols found" messages. I can imagine
someone down the road finding another use for wanting to know what the
system libraries are considered to be, but using "set system-library"
will mess with the "no debugging" suppression. One could add an
additional option, set print system-library-symbol-loading on|off" (or
some such) akin to the current "set print symbol-loading on|off", or
change the latter to "set print symbol-loading off|normal|all" (or
some such, I didn't spend any time here thinking of good names :-)).
[The option was added after 6.8 so we should be able to change it
before the next release.]
Having to specify what the system library paths are is another
configuration parameter for ports, and if it's just used to suppress
"no debugging symbols found", I wonder if it's worth it though.
next prev parent reply other threads:[~2008-11-24 16:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 16:49 Mark Kettenis
2008-11-22 17:49 ` Doug Evans
2008-11-22 21:41 ` Eli Zaretskii
2008-11-24 3:23 ` Paul Pluzhnikov
2008-11-24 16:54 ` Eli Zaretskii
2008-11-24 19:42 ` Doug Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 19:24 Mark Kettenis
2008-11-21 22:08 ` Eli Zaretskii
2008-11-22 4:43 ` Doug Evans
2008-11-22 6:38 ` Eli Zaretskii
2008-10-03 21:35 Doug Evans
2008-10-30 5:19 ` Joel Brobecker
2008-11-07 22:45 ` Doug Evans
2008-11-08 9:15 ` Eli Zaretskii
2008-11-10 16:46 ` Daniel Jacobowitz
2008-11-10 18:32 ` Joel Brobecker
2008-11-10 20:33 ` Eli Zaretskii
2008-11-10 20:51 ` Daniel Jacobowitz
2008-11-11 5:03 ` Eli Zaretskii
2008-11-11 5:34 ` Daniel Jacobowitz
2008-11-21 18:46 ` Doug Evans
2008-11-21 19:16 ` Eli Zaretskii
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=e394668d0811240819o2b7da132xe8150c9cc8e97c4c@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=ppluzhnikov@google.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