From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, jnordby@caspiannetworks.com
Cc: gdb@sources.redhat.com
Subject: Re: Searching for pattern in memory from GDB?
Date: Mon, 08 Apr 2002 12:12:00 -0000 [thread overview]
Message-ID: <200204081912.g38JCcK16579@duracef.shout.net> (raw)
You can build your executable file with symbols, then strip the symbols
and ship it. Then run gdb on the unstripped executable and the core
dump from the stripped executable.
You could do this:
static char signpost [64];
sprintf (signpost, "\nFOO_BUFFER_ADDRESS=0x%p\n", foo_buffer_address);
Then when you get the core dump, you can do:
strings -a core | grep FOO_BUFFER_ADDRESS
If your target operating system(s) support mmap at a fixed address,
then you can mmap to that address. Obviously that is not portable but
if it works, it works. That would make it exceptionally easy to attach
to a running process.
Hope this helps,
Michael C
next reply other threads:[~2002-04-08 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 12:12 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 11:41 James Nordby
2002-04-08 11:47 ` Daniel Jacobowitz
2002-04-11 14:45 ` Michael Snyder
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=200204081912.g38JCcK16579@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jnordby@caspiannetworks.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