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: Thu, 12 Jun 2008 14:30:00 -0000 [thread overview]
Message-ID: <200806121430.m5CEUAF3021413@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <1213280300.18445.1.camel@gargoyle.br.ibm.com> from "Luis Machado" at Jun 12, 2008 11:18:20 AM
Luis Machado wrote:
> Does the libraries' mappings correspond exactly to what we had before in
> the output of "info proc mappings" for the live process? Right before
> the core file was generated?
Well, it corresponds exactly to what "info target" would have shown on
the live process. Of course, "info target" and "info proc mappings"
show somewhat different information; "info target" displays *sections*
retrieved from loaded symbol files, while "info proc mappings" display
memory maps as reported by the kernel -- these correspond to the
*segments* (not sections) of ELF files, and in addition show other
maps (e.g. stack, heap, mmap, ...).
What I'm wondering is basically whether for your purposes, you really
need the segment/mapping information, or whether section data as shown
by "info target" is sufficient.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2008-06-12 14:30 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
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 [this message]
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=200806121430.m5CEUAF3021413@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