From: Daniel Jacobowitz <drow@false.org>
To: Jan Somr <SomrJ@seznam.cz>
Cc: gdb@sourceware.org
Subject: Re: GDB and mmap
Date: Fri, 13 Jul 2007 11:44:00 -0000 [thread overview]
Message-ID: <20070713114445.GA970@caradoc.them.org> (raw)
In-Reply-To: <26.140-15180-2028046551-1184314506@seznam.cz>
On Fri, Jul 13, 2007 at 10:15:06AM +0200, Jan Somr wrote:
> Hi all, please help.
> I have an application which makes cores and uses mapped memory (mmap). How can I access this memory in GDB?
> When I try print it I get this message: "Cannot access memory at address xxxxxxxxxx". Is the shared memory dumped in the core?
No, it usually is not dumped. There's nothing GDB can do about that.
Some operating systems have configuration options to control what is
dumped.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-13 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 8:15 Jan Somr
2007-07-13 11:44 ` Daniel Jacobowitz [this message]
2007-07-17 3:46 ` Rodrigo Rubira Branco
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 12:19 gdb " David Stroupe
2002-05-13 12:24 ` Daniel Jacobowitz
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=20070713114445.GA970@caradoc.them.org \
--to=drow@false.org \
--cc=SomrJ@seznam.cz \
--cc=gdb@sourceware.org \
/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