From: Mihai Basa <Mihai.Basa@NUIGALWAY.IE>
To: gdb@sources.redhat.com
Subject: Auto-deleting watchpoints
Date: Tue, 02 Dec 2003 20:38:00 -0000 [thread overview]
Message-ID: <3FCC0BA0@bodkin.nuigalway.ie> (raw)
Greetings all!
I'd like to question a certain behaviour of gdb, and I quote from the
man(ual):
"GDB automatically deletes watchpoints that watch local (automatic)
variables, or expressions that involve such variables, when they go out
of scope, that is, when the execution leaves the block in which these
variables were defined."
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!
I am not totally aware about the way hardware watchpoints behave when the
processor switches Code-Segments (which is what happens?), but couldn't gdb at
least re-enable the watchpoint when it re-enters scope? Is there a bad
side-effect to this that I can't see?
Highest regards!
Mihai Basa
next reply other threads:[~2003-12-02 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 20:38 Mihai Basa [this message]
2003-12-02 20:44 ` Daniel Jacobowitz
2003-12-03 5:36 ` Eli Zaretskii
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=3FCC0BA0@bodkin.nuigalway.ie \
--to=mihai.basa@nuigalway.ie \
--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