Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix Solaris gcore / shared libraries interaction
Date: Sun, 22 Nov 2009 14:35:00 -0000	[thread overview]
Message-ID: <20091122143421.GA18630@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0911210009070.4910@digraph.polyomino.org.uk>

Hi Joseph,


On Sat, 21 Nov 2009 01:10:27 +0100, Joseph S. Myers wrote:
> With some versions of the Solaris 10 dynamic linker, if you create a
> core file with GDB's gcore command and then load that core file into
> GDB, you get warnings of the form
> 
> warning: Can't read pathname for load map: I/O error.

The exactly the same problem+reasons affects not only GNU/Linux gcore but also
native kernel core dumps:

* glibc insists its behavior is correct
  http://sourceware.org/ml/libc-alpha/2009-10/msg00001.html

* 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


Thanks,
Jan


  reply	other threads:[~2009-11-22 14:35 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 [this message]
2009-11-22 15:12   ` Joseph S. Myers
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=20091122143421.GA18630@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@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