From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Group errors for many missing shared libraries
Date: Mon, 12 Apr 2010 20:32:00 -0000 [thread overview]
Message-ID: <m3sk70csyr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201004121130.03196.pedro@codesourcery.com> (Pedro Alves's message of "Mon, 12 Apr 2010 11:30:03 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> warning: Could not load shared library symbols for 10 libraries, e.g. /lib/libncurses.so.5.
Pedro> Do you need "set solib-search-path" or "set sysroot"?
I think it is a definite improvement.
Pedro> You can later still do "info sharedlibrary" to check
Pedro> exactly which shared libraries don't have symbols read in:
How about mentioning this in the message if there is more than one
missing?
Tom
next prev parent reply other threads:[~2010-04-12 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 10:30 Pedro Alves
2010-04-12 20:32 ` Tom Tromey [this message]
2010-04-13 10:15 ` Pedro Alves
2010-04-13 21:00 ` Tom Tromey
2010-04-14 13:53 ` Pedro Alves
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=m3sk70csyr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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