Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Watching expressions that don't involve memory (e.g., watch $regfoo)
Date: Thu, 04 Mar 2010 02:05:00 -0000	[thread overview]
Message-ID: <4B8F155E.8050209@vmware.com> (raw)
In-Reply-To: <201003040156.44957.pedro@codesourcery.com>

Pedro Alves wrote:
> Anyone else things this is useful?  Here's a 5 minute hack at it.
> 
> It allows for e.g.:
> 
> (top-gdb) watch $rax
> Watchpoint 4: $rax
> (top-gdb) c
> Continuing.
> Watchpoint 4: $rax
> 
> Old value = 11802104
> New value = 140737488347216
> 0x0000000000456647 in main (argc=1, argv=0x7fffffffe158) at ../../src/gdb/gdb.c:28
> 28        memset (&args, 0, sizeof args);
> (top-gdb)
> 
> Current GDB will successfuly create the watchpoint in the
> breakpoint list, but it never triggers, because since the
> watchpoint isn't watching any memory, it ends up with
> no bp_location associated.
> 
> 
> For extra fun, even watching $_siginfo works.

I think watching registers, or expressions involving registers
(such as $sp > 0x10000000) could be incredibly useful.

Expressions on a varobj sound useful to watch too.

One question; what will happen if I watch a constant?



  reply	other threads:[~2010-03-04  2:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  1:57 Pedro Alves
2010-03-04  2:05 ` Michael Snyder [this message]
2010-03-04  2:13   ` Pedro Alves
2010-03-04  4:12 ` Eli Zaretskii
2010-03-04 13:16   ` Pedro Alves
2010-03-04 14:11     ` Eli Zaretskii
2010-03-04 15:39       ` Pedro Alves
2010-03-04  5:30 ` Joel Brobecker
2010-03-04  7:40   ` Eli Zaretskii

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=4B8F155E.8050209@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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