From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: bruce.korb@gmail.com, gdb@sourceware.org
Subject: Re: How can I get a memory map out of a core file?
Date: Sat, 07 Jun 2008 06:30:00 -0000 [thread overview]
Message-ID: <u1w39oj06.fsf@gnu.org> (raw)
In-Reply-To: <1212789259.3601.426.camel@localhost.localdomain>
> From: Michael Snyder <msnyder@specifix.com>
> Cc: gdb@sourceware.org
> Date: Fri, 06 Jun 2008 14:54:19 -0700
>
> On Fri, 2008-06-06 at 13:45 -0700, Bruce Korb wrote:
> > Hi,
> >
> > "jmap" looked really nice, but that is Solaris only.
> > "pmap" is almost what I want, but there's no /proc/pid directory
> > for my core dump any more.
> > If there is some GDB command I can use, I haven't found it.
> > I haven't seen any obvious way to emulate it either.
> > Surely someone, somewhere has solved this problem.
> > Anyone know where the solution is hiding? :)
> > Thank you. Regards - Bruce
>
> Try "help info proc mappings". It may be the closest we've got
> to what you want.
How can this help in a core file? The process is already dead, so
it's not in /proc, right? Or am I missing something?
next prev parent reply other threads:[~2008-06-07 6: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 [this message]
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
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=u1w39oj06.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bruce.korb@gmail.com \
--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