public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Nick Clifton <nickc@redhat.com>
Cc: davidm@napali.hpl.hp.com, gdb@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: [davidm@napali.hpl.hp.com: readelf question]
Date: Tue, 17 Jun 2003 18:56:00 -0000	[thread overview]
Message-ID: <16111.25674.965375.967286@napali.hpl.hp.com> (raw)
In-Reply-To: <m38ys1unuo.fsf@redhat.com>

Hi Nick,

>>>>> On Tue, 17 Jun 2003 09:09:35 +0100, Nick Clifton <nickc@redhat.com> said:

  Nick> Hi David,
  >> Another toolchain question: with the latest 2.5 kernel, coredumps
  >> will cover the kernel shared library describing the gate page (aka
  >> "gate DSO").  Unfortunately, readelf -a prints a warning message
  >> when reading such coredumps:

  Nick> Is it possible for you to generate a *small* example core file which
  Nick> demonstrates this problem and post it to the list ?  If not, could you
  Nick> make one available for retrieval via ftp/http ?

Certainly.  I meant to do that with the original report, but seem to
have forgotten... ;-(

Anyhow, I now attached two files:

 core-static.gz	compressed core file for a statically linked app doing abort()
 core-static.gz	same app but dynamically linked

It doesn't seem to make much of a difference whether the file is
statically or dynamically linked, but I thought it would be best to
cover both cases.

Please let me know if you need anything else.

Thanks,

	--david

Attachment:
core-static.gz
Description: core-static.gz
Attachment:
core-dynamic.gz
Description: core-dynamic.gz

  reply	other threads:[~2003-06-17 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 14:57 H. J. Lu
2003-06-17  8:14 ` Nick Clifton
2003-06-17 18:56   ` David Mosberger [this message]
2003-06-17 19:27     ` Andrew Cagney
2003-06-17 20:14       ` David Mosberger
2003-06-17 20:41         ` Andrew Cagney
2003-06-17 20:44         ` Roland McGrath
2003-06-17 21:00           ` David Mosberger
2003-06-17 21:15             ` Andrew Cagney
2003-06-17 21:06           ` Daniel Jacobowitz
2003-06-17 20:26 ` Roland McGrath

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=16111.25674.965375.967286@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).