From: Pawel <paulino90@tenbit.pl>
To: gdb mailing list <gdb@sourceware.org>
Subject: gdb: debugging memory location changes.
Date: Wed, 20 Jun 2007 09:42:00 -0000 [thread overview]
Message-ID: <18040.63313.819789.233867@localhost.localdomain> (raw)
Hallo Group Members.
I have the following problem.
I am debugging large code I am not familiar with. I noticed that
memory location, for example funnyObject.field, changes somewhere in
the code and I do not know where, thus I do not know where to set the
breakpoint. Can gdb find such places in the code for me?
Regards, Pawel
next reply other threads:[~2007-06-20 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 9:42 Pawel [this message]
2007-06-20 10:00 ` Nick Roberts
2007-06-22 20:00 ` Pawel
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=18040.63313.819789.233867@localhost.localdomain \
--to=paulino90@tenbit.pl \
--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