From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: msnyder@redhat.com
Cc: mec@shout.net, fnf@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix problem with watchpoint test in gdb.base/commands.exp
Date: Thu, 02 May 2002 23:46:00 -0000 [thread overview]
Message-ID: <5137-Fri03May2002094432+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3CD18056.893FE00F@redhat.com> (message from Michael Snyder on Thu, 02 May 2002 11:07:18 -0700)
> Date: Thu, 02 May 2002 11:07:18 -0700
> From: Michael Snyder <msnyder@redhat.com>
> >
> > Btw, I think this is a misfeature: GDB should disable the watchpoints,
> > but not delete them.
>
> Hmmm... I thought that was (effectively) what happened.
> I know there's an invisible "out of scope" breakpoint sometimes,
> and I thought it was that breakpoint that was deleted, not the
> watchpoint itself. Was I wrong?
It looks like that. Try this:
- write a simple program whose `main' assigns a value to a variable;
- run the program to the entry to `main', then set a hardware
watchpoint to watch that variable;
- continue the program, and when the watchpoint is hit, continue it
again;
- when `main' is exited, GDB says the watchpoint was deleted;
- try "info watchpoints" -- you won't see the watchpoint;
- try rerunning the program -- the watchpoint won't be hit.
So my conclusion is that the watchpoint is really deleted, not just
disabled and/or made invisible. For watchpoints which are hard to
set up (perhaps for some complicated expression or with complex
conditions), that is a nuisance.
next prev parent reply other threads:[~2002-05-03 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 8:34 Michael Elizabeth Chastain
2002-05-02 8:43 ` Andrew Cagney
2002-05-02 8:50 ` Eli Zaretskii
2002-05-02 11:23 ` Michael Snyder
2002-05-02 23:46 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-02 8:48 Michael Elizabeth Chastain
2002-05-02 11:22 ` Michael Snyder
2002-05-01 16:48 Fred Fish
2002-05-01 16:58 ` Michael Snyder
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=5137-Fri03May2002094432+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=fnf@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
--cc=msnyder@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