From: Michael Snyder <msnyder@specifix.com>
To: Yakov Lerner <iler.ml@gmail.com>
Cc: Andreas Schwab <schwab@suse.de>, gdb@sourceware.org
Subject: Re: guessing where address belongs to
Date: Thu, 06 Mar 2008 20:37:00 -0000 [thread overview]
Message-ID: <1204835291.19253.691.camel@localhost.localdomain> (raw)
In-Reply-To: <f36b08ee0803060245k1f52397hc2a8b3639b61294b@mail.gmail.com>
On Thu, 2008-03-06 at 12:45 +0200, Yakov Lerner wrote:
> On Thu, Mar 6, 2008 at 12:05 PM, Andreas Schwab <schwab@suse.de> wrote:
> > "Yakov Lerner" <iler.ml@gmail.com> writes:
> >
> > > Gdb has no integration with malloc, correct ?
> > > Gdb has no way of enumerating all malloced
> > > pieces ("heap objects"), correct ?
> > >
> > > Or gdb does have a way of guessing which "heap
> > > object" some address X (that points inside the heap) belongs to ?
> >
> > The details are highly dependent on the malloc implementation. There is
> > no way to find that out without intimate knowledge of the
> > implementation.
>
> You don't need details of malloc guts for that.
>
> It's enough to hook to the entry and return from malloc,free,realloc.
Yep, and there are tools that do that -- but gdb isn't one of them.
OTOH, it would be possible to set user breakpoints at malloc and
free, and then write user gdb commands to collect whatever
information you want...
next prev parent reply other threads:[~2008-03-06 20:28 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
[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 [this message]
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=1204835291.19253.691.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb@sourceware.org \
--cc=iler.ml@gmail.com \
--cc=schwab@suse.de \
/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