This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: How can I get a memory map out of a core file?
- From: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- To: luisgpm at linux dot vnet dot ibm dot com
- Cc: drow at false dot org (Daniel Jacobowitz), bruce dot korb at gmail dot com (Bruce Korb), schwab at suse dot de (Andreas Schwab), gdb at sourceware dot org, eliz at gnu dot org (Eli Zaretskii), msnyder at specifix dot com (Michael Snyder)
- Date: Mon, 9 Jun 2008 19:51:28 +0200 (CEST)
- Subject: Re: How can I get a memory map out of a core file?
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