From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Jonas Maebe <jonas.maebe@elis.ugent.be>
Subject: Re: Run until some FPU register has changed
Date: Fri, 04 Nov 2011 18:37:00 -0000 [thread overview]
Message-ID: <201111041837.01387.pedro@codesourcery.com> (raw)
In-Reply-To: <6C87CB2A-8D2C-4B03-AEBC-7A5A7562864C@elis.ugent.be>
On Friday 04 November 2011 17:55:12, Jonas Maebe wrote:
>
> On 04 Nov 2011, at 18:47, Thomas Baruchel wrote:
>
> > "run until register 0 in FPU has changed"
>
> The "watch" command also works with registers, so
> watch $f0
> c
>
> should work (replace f0 with the actual name of floating point register 0). You can oif course set watchpoints on all floating point registers, although I don't know how much extra slowdown that will cause.
I assume pretty much negligible compared to watching a single register.
GDB will need to force single-stepping of the target behind the scenes in
both cases, and pulling a single float register out of the target is
already likely pulling them all.
--
Pedro Alves
prev parent reply other threads:[~2011-11-04 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 17:04 Recursive call to stepi and "Max user call depth exceeded" Thomas Baruchel
2011-11-04 17:23 ` Pedro Alves
2011-11-04 17:47 ` Run until some FPU register has changed Thomas Baruchel
2011-11-04 17:55 ` Jonas Maebe
2011-11-04 18:37 ` Pedro Alves [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=201111041837.01387.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jonas.maebe@elis.ugent.be \
/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