public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/11021] watch foo(x) -> infinite recursion
Date: Sat, 14 Aug 2010 03:03:00 -0000	[thread overview]
Message-ID: <20100814030335.20226.qmail@sourceware.org> (raw)
In-Reply-To: <20091125214957.11021.ppluzhnikov@google.com>


------- Additional Comments From pedro at codesourcery dot com  2010-08-14 03:03 -------
Yeah, I saw this too today.

This is most probably gdb evaluating the expression when the call dummy
breakpoint is hit.  Maybe we should skip that if we hit the call dummy
breakpoint (and we're not stopping for any other reason).  May be tricky to
get right.  Hmm, with software watchpoints it may even be impossible to
get right.

There's the option of detecting this at watchpoint creation time,
and just say you can't do that Dave.  Better than what we have today.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1


http://sourceware.org/bugzilla/show_bug.cgi?id=11021

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2010-08-14  3:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 21:49 [Bug breakpoints/11021] New: " ppluzhnikov at google dot com
2010-08-14  3:03 ` pedro at codesourcery dot com [this message]
     [not found] <bug-11021-4717@http.sourceware.org/bugzilla/>
2013-08-30 14:47 ` [Bug breakpoints/11021] " msaleem at codesourcery dot com
2013-09-02 10:16 ` msaleem at codesourcery dot com

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=20100814030335.20226.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).