From: Michael Snyder <msnyder@specifix.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yakov Lerner <iler.ml@gmail.com>, gdb@sourceware.org
Subject: Re: guessing where address belongs to
Date: Wed, 05 Mar 2008 19:56:00 -0000 [thread overview]
Message-ID: <1204746687.19253.610.camel@localhost.localdomain> (raw)
In-Reply-To: <uhcfmi8dh.fsf@gnu.org>
On Tue, 2008-03-04 at 21:42 +0200, Eli Zaretskii wrote:
> > Date: Tue, 4 Mar 2008 10:15:42 +0200
> > From: "Yakov Lerner" <iler.ml@gmail.com>
> >
> > Is there command to have gdb guess which memory object this
> > address belongs to (which function ... which stack frame .. which static
> > object .. which head object )?
>
> I think you want "info symbol".
That will help -- if the address is associated with a symbol.
For stack and heap pointers it's not always helpful.
I don't think there is a single command to do what you want,
but "info target" will be helpful -- it will show all loaded
sections and their memory ranges. You can fit the address into
one of them (if it fits). "info file" is an alias for this
(I think).
This shows the sections for shared libraries too, which is a plus.
Maybe if you can mock up a spec for what it is you want,
it wouldn't be that difficult to implement a new command
for it...
next prev parent reply other threads:[~2008-03-05 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 9:21 Yakov Lerner
2008-03-04 8:16 ` Yakov Lerner
2008-03-04 9:51 ` Andreas Schwab
2008-03-05 16:15 ` Eli Zaretskii
2008-03-05 19:56 ` Michael Snyder [this message]
[not found] ` <f36b08ee0803052138u6749eoba4d0186afb7ecbc@mail.gmail.com>
2008-03-06 6:54 ` Yakov Lerner
2008-03-06 10:46 ` Andreas Schwab
2008-03-06 13:13 ` Yakov Lerner
2008-03-06 20:37 ` Michael Snyder
2008-03-06 20:28 ` Michael Snyder
2008-03-06 20:27 ` 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=1204746687.19253.610.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=iler.ml@gmail.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