From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org, kevinb@redhat.com
Subject: Re: RFA: More concise errors for missing shared libraries
Date: Sat, 13 May 2006 09:13:00 -0000 [thread overview]
Message-ID: <200605130912.k4D9CLWI017276@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060509174426.GA9730@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 9 May 2006 13:44:26 -0400)
> Date: Tue, 9 May 2006 13:44:26 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> One of the quirks of SymbianOS compared to a traditional hosted target is
> that it's quite likely that GDB will have no symbol file at all for many of
> the loaded libraries. A ROM image may contain many DLLs, presented as a
> virtual filesystem, which are effectively preloaded into the memory space of
> every process. A user probably only has symbol files for his own DLLs, not
> the DLLs which provide operating system services. So, the behavior of GDB
> when shared libraries can not be found is much more important than on other
> targets.
Did you consider providing stub ELF libraries for the system DLL's too?
> Right now this is really noisy. We get a two-line error message for each
> library from update_solib_list when we detect the new library, and another
> one from solib_read_symbols later. This patch condenses those into a single
> warning:
>
> warning: Could not load shared library symbols for 2 libraries, e.g. /lib/libnss_dns.so.2.
> Do you need "set solib-search-path" or "set solib-absolute-prefix"?
I think this is bad. I really hate it when tools give me incomplete
error information. Consider the situation where I have set
solib-search-path/solib-absolute-prefix, but only have a subset of the
libraries available. I go and install libnss_dns.so.2, but I have no
clue what the other library is. I have to rerun the program in GDB to
find out the name of the other library.
To reduce the clutter, I think we should not print the
Do you need "set solib-search-path" or "set solib-absolute-prefix"?
suggestion for every shared library, but only once, preferably at the
end of of all output.
If that would still provide too much clutter, we should perhaps
introduce a user-settable limit for these.
Mark
next prev parent reply other threads:[~2006-05-13 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 17:44 Daniel Jacobowitz
2006-05-10 21:11 ` Jim Blandy
2006-05-13 9:13 ` Mark Kettenis [this message]
2006-05-13 22:11 ` Daniel Jacobowitz
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=200605130912.k4D9CLWI017276@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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