Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: luisgpm@linux.vnet.ibm.com
Cc: drow@false.org (Daniel Jacobowitz),
	bruce.korb@gmail.com (Bruce Korb),
	        schwab@suse.de (Andreas Schwab),
	gdb@sourceware.org,         eliz@gnu.org (Eli Zaretskii),
	msnyder@specifix.com (Michael Snyder)
Subject: Re: How can I get a memory map out of a core file?
Date: Mon, 09 Jun 2008 17:52:00 -0000	[thread overview]
Message-ID: <200806091751.m59HpSSv020533@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <1213028867.10042.101.camel@gargoyle> from "Luis Machado" at Jun 09, 2008 01:27:47 PM

Luis Machado wrote:

> Yes. Mainly giving the user the option to show exactly what we had
> in /proc/<pid>/maps right before the crash, so we know where things were
> in memory, like the heap, stack and some specific shared libraries'
> mappings. 
> 
> We currently can't do that. There's some information in the program
> headers from a core file, like the one below, that show us a bit of
> mapping-related information, but not enough so we can actually track
> them down to a shared library.

But shared library information should be available via 
"info sharedlibrary" (which uses the in-memory data structures
allocated by ld.so, which are present in the core file) ...

What is the extra information /proc/<pid>/maps provides that 
you're concerned about?

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-06-09 17:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 20:46 Bruce Korb
2008-06-06 21:54 ` Michael Snyder
2008-06-07  6:30   ` Eli Zaretskii
2008-06-07 16:31     ` Bruce Korb
2008-06-07 16:58       ` Eli Zaretskii
2008-06-07 18:14       ` Brian Dessent
2008-06-07 18:29         ` Andreas Schwab
2008-06-07 20:01           ` Bruce Korb
2008-06-09 15:04             ` Luis Machado
2008-06-09 15:24               ` Daniel Jacobowitz
2008-06-09 15:32                 ` Luis Machado
2008-06-09 15:40                   ` Daniel Jacobowitz
2008-06-09 16:28                     ` Luis Machado
2008-06-09 17:52                       ` Ulrich Weigand [this message]
2008-06-09 18:03                         ` Luis Machado
2008-06-12 13:58                           ` Ulrich Weigand
2008-06-12 14:18                             ` Luis Machado
2008-06-12 14:30                               ` Ulrich Weigand
2008-06-09 22:32                       ` Michael Snyder
2008-06-09 15:37                 ` Bruce Korb

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=200806091751.m59HpSSv020533@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=bruce.korb@gmail.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    --cc=msnyder@specifix.com \
    --cc=schwab@suse.de \
    /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