From: Jim Blandy <jimb@codesourcery.com>
To: "ying lcs" <yinglcs@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Can i set a breakpoint when a member of a C struct is being assigned?
Date: Mon, 30 Jul 2007 21:17:00 -0000 [thread overview]
Message-ID: <m3ps29lhhy.fsf@codesourcery.com> (raw)
In-Reply-To: <568e62a40707292020j4e53d480je8822ac6f37f4eda@mail.gmail.com> (ying lcs's message of "Sun, 29 Jul 2007 22:20:58 -0500")
"ying lcs" <yinglcs@gmail.com> writes:
> Can i set a breakpoint when a member of a C struct is being assigned?
>
> For example, i have a C struct in my code:
> struct myStruct{
> int type;
> };
There isn't any way to set a breakpoint on all assignments to a chosen
member of a chosen structure type, regardless of which actual object
of that type is being modified.
You can set a watchpoint on a particular member of a particular
object; see the GDB manual on 'watchpoints'.
You can, of course, set a breakpoint on a particular assignment
statement.
prev parent reply other threads:[~2007-07-30 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 5:37 ying lcs
2007-07-30 9:32 ` Bernhard Walle
2007-07-30 21:16 ` Eli Zaretskii
2007-07-30 21:17 ` Jim Blandy [this message]
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=m3ps29lhhy.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=yinglcs@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