From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix Solaris gcore / shared libraries interaction
Date: Sun, 22 Nov 2009 15:12:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0911221503570.26496@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20091122143421.GA18630@host0.dyn.jankratochvil.net>
On Sun, 22 Nov 2009, Jan Kratochvil wrote:
> * core dumping in Linux kernel could be fixed but a patch containing similar
> deep understanding of link_map was already rejected before so I doubt this
> one would get accepted.
>
> Isn't suitable the GDB change for the core file loading never replied here?
> [patch] Fix GNU/Linux core open: Can't read pathname for load map: Input/output error.
> http://sourceware.org/ml/gdb-patches/2009-10/msg00142.html
On older GDB sources, I observed more warnings than those I quoted:
warning: Can't read pathname for load map: I/O error.
Reading symbols from /lib/64/libc.so.1...done.
Loaded symbols for /lib/64/libc.so.1
warning: Can't read pathname for load map: I/O error.
warning: Unable to find dynamic linker.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
and "info shared" repeated the warning and did not show the dynamic
linker, which suggested that things needed to be fixed so it could find
this path, rather than just suppressing a warning.
For some reason, current FSF GDB sources do not produce all these extra
warnings.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-11-22 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 0:11 Joseph S. Myers
2009-11-22 14:35 ` Jan Kratochvil
2009-11-22 15:12 ` Joseph S. Myers [this message]
2009-11-22 15:19 ` Daniel Jacobowitz
2009-11-22 16:04 ` Jan Kratochvil
2009-11-22 16:54 ` Joseph S. Myers
2009-11-28 20:11 ` Ping " Joseph S. Myers
2009-12-01 20:09 ` 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=Pine.LNX.4.64.0911221503570.26496@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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