From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <dje@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 03:23:00 -0000 [thread overview]
Message-ID: <8ac60eac0811221107s47cd5d30o472a46842a5a33ed@mail.gmail.com> (raw)
In-Reply-To: <uskpkhszs.fsf@gnu.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 "*".
[Use ';' instead of space to separate patterns on *win* targets.]
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2008-11-22 19:08 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 [this message]
2008-11-24 16:54 ` Eli Zaretskii
2008-11-24 19:42 ` Doug Evans
-- 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=8ac60eac0811221107s47cd5d30o472a46842a5a33ed@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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