From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCHv4] gdb: Add default frame methods to gdbarch
Date: Sun, 09 Sep 2018 02:54:00 -0000 [thread overview]
Message-ID: <878t4b5qix.fsf@tromey.com> (raw)
In-Reply-To: <f1e6e25725ca475f142a801cb3c46101@polymtl.ca> (Simon Marchi's message of "Sun, 09 Sep 2018 00:52:43 +0100")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
Simon> Ok, that's interesting. My hypothesis is that when GDB needs to watch
Simon> an expression (a + b + c), it probably looks at the all_values chain
Simon> to know all the intermediary values (that represent a memory location
Simon> or a register) that were read from the target to evaluate that
Simon> expression. It then puts some hardware or software watches on these
Simon> memory locations or registers. So if the values chain contains a
Simon> value representing something we don't really watch to watch (such as
Simon> fp or sp, according to the comment), GDB would watch it, even though
Simon> it doesn't really affect the result of the expression. That's just my
Simon> guess.
Yes, that's correct.
Simon> I am fine with that (unless someone who really knows this comes up
Simon> with a better explanation). Since it just causes the value we don't
Simon> need anymore to be deleted immediatly, it should be harmless.
I agree.
Tom
prev parent reply other threads:[~2018-09-09 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 21:26 Andrew Burgess
2018-09-08 22:06 ` Simon Marchi
2018-09-08 23:19 ` Andrew Burgess
2018-09-08 23:52 ` Simon Marchi
2018-09-09 2:54 ` Tom Tromey [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=878t4b5qix.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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