From: Eli Zaretskii <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Mihai.Basa@NUIGALWAY.IE, gdb@sources.redhat.com
Subject: Re: Auto-deleting watchpoints
Date: Wed, 03 Dec 2003 05:36:00 -0000 [thread overview]
Message-ID: <uekvm5ule.fsf@elta.co.il> (raw)
In-Reply-To: <20031202204451.GA14313@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 2 Dec 2003 15:44:51 -0500)
> Date: Tue, 2 Dec 2003 15:44:51 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> >
> > This includes deleting local watchpoints even when the program makes a call to
> > a library function (say, sqrt()). I believe this auto-deletion _severly_
> > reduces the practicality of watchpoints, because they simply go away on the
> > first call they hit!
>
> That is not what is supposed to happen. The watchpoint should stay
> until the function containing the local variable has exited.
Right. And I have simple test cases to prove it.
Mihai, you probably discovered a bug. Please send a test case.
next prev parent reply other threads:[~2003-12-03 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 20:38 Mihai Basa
2003-12-02 20:44 ` Daniel Jacobowitz
2003-12-03 5:36 ` Eli Zaretskii [this message]
2003-12-04 16:58 Mihai Basa
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=uekvm5ule.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=Mihai.Basa@NUIGALWAY.IE \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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