Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH] Skip VDSO when reading SO list
Date: Mon, 19 Aug 2013 18:30:00 -0000	[thread overview]
Message-ID: <20130819182907.GA2145@host2.jankratochvil.net> (raw)
In-Reply-To: <87d2p9oi4i.fsf@br87z6lw.de.ibm.com>

On Mon, 19 Aug 2013 16:44:13 +0200, Andreas Arnez wrote:
> On some Linux versions, the file name (l_name) of a VDSO's link map
> entry lies in read-only memory that is excluded from a core dump.
> When reading such a core dump, GDB complains:
> 
> warning: Can't read pathname for load map: Input/output error.

I believe the right fix is in glibc instead:
	[patch] Fix vDSO l_name for GDB's: Can't read pathname for load map:Input/output error.
	http://sourceware.org/ml/libc-alpha/2009-10/msg00001.html
	Message-ID: <20091004161706.GA27450@host0.dyn.jankratochvil.net>

Could you verify it works for you so that we could possibly ping it?

Fedora is using a similar patch but that is IMO a wrong workaround:
	http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-core-open-vdso-warning.patch



Thanks,
Jan


  reply	other threads:[~2013-08-19 18:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 14:44 Andreas Arnez
2013-08-19 18:30 ` Jan Kratochvil [this message]
2013-08-19 20:42   ` Joel Brobecker
2013-08-19 20:47     ` Jan Kratochvil
2013-08-19 21:13       ` Joel Brobecker
2013-08-20 11:44   ` Andreas Arnez
2013-08-20 13:47   ` Jan Kratochvil
2013-09-20 13:15 ` Jan Kratochvil
2013-09-20 15:27   ` Jan Kratochvil
2013-09-20 17:00   ` Andreas Arnez
2013-09-20 18:14     ` Jan Kratochvil

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=20130819182907.GA2145@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=krebbel@linux.vnet.ibm.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