Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix GNU/Linux core open: Can't read pathname for load map: Input/output error.
Date: Tue, 17 May 2011 18:58:00 -0000	[thread overview]
Message-ID: <BANLkTinAu3KxFBRYmYvsf7ocJ1tY0ShHGA@mail.gmail.com> (raw)
In-Reply-To: <20110517170849.GA2463@host1.jankratochvil.net>

On Tue, May 17, 2011 at 10:08 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Tue, 17 May 2011 03:06:11 +0200, Paul Pluzhnikov wrote:
>> I see this all the time, and it causes end-user confusion.
>
> (a)
> The fix should be in glibc and not in gdb but it was rejected in glibc.

In this particular case I believe Ulrich may be correct in rejecting
the patch.

> (b)
> Loading libraries for a core file from the inferior solist stored in the core
> file does not work anyway.  If you have a crashed application with memory
> corruption commonly the inferior solist is also corrupted,

While it's very possible for solist in the inferior to be corrupted, I've
never actually seen this happen in practice, and I do regularly look at
core dumps.

I wonder what makes corrupt solist in the inferior common for you.

> The right approach is to map symbols for libraries according to their
> build-ids (when available).

But until then, IWBN to not issue a warning in the common case.

-- 
Paul Pluzhnikov


  reply	other threads:[~2011-05-17 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 21:46 Jan Kratochvil
2011-05-17  1:07 ` Paul Pluzhnikov
2011-05-17 17:09   ` Jan Kratochvil
2011-05-17 18:58     ` Paul Pluzhnikov [this message]
2011-05-17 19:03       ` 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=BANLkTinAu3KxFBRYmYvsf7ocJ1tY0ShHGA@mail.gmail.com \
    --to=ppluzhnikov@google.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