From: Brian Dessent <brian@dessent.net>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Michael Snyder <msnyder@specifix.com>,
gdb@sourceware.org
Subject: Re: How can I get a memory map out of a core file?
Date: Sat, 07 Jun 2008 18:14:00 -0000 [thread overview]
Message-ID: <484AD008.8845E46E@dessent.net> (raw)
In-Reply-To: <200806070930.21380.Bruce.Korb@gmail.com>
Bruce Korb wrote:
> was attempted. So, for me, the ideal solution is a command that yields
> (figures out) the valid address ranges, and an adequate backup would
Doesn't "info target" do this?
$ ulimit -c 10000; top & kill -ABRT $! && fg %1
[1] 2347
top
Aborted (core dumped)
$ gdb -batch -x <(echo 'info target') -c core
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
Core was generated by `top'.
Program terminated with signal 6, Aborted.
#0 0x40000c20 in ?? ()
Local core dump file:
`/home/brian/core', file type elf32-i386.
0x08054000 - 0x08055000 is load2
0x08055000 - 0x08058000 is load3
0x40016000 - 0x40017000 is load5
0xbffff000 - 0xc0000000 is load6
0xffffe000 - 0xfffff000 is load7
Though I suppose those section names are not really all that useful, but
in conjunction with the executable it should be possible to reverse
engineer which library / executable each corresponds to.
Brian
next prev parent reply other threads:[~2008-06-07 18:14 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 [this message]
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
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=484AD008.8845E46E@dessent.net \
--to=brian@dessent.net \
--cc=bruce.korb@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=msnyder@specifix.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