From: "Charlls Quarra" <charlls_quarra@yahoo.com.ar>
To: gdb@sources.redhat.com
Subject: detecting breakpoint type and number
Date: Wed, 14 Jul 2004 23:09:00 -0000 [thread overview]
Message-ID: <20040714230107.40234.qmail@web41813.mail.yahoo.com> (raw)
Hi,
I have a script that continues on a watchpointed
variable untils its value becomes something expected.
the script looks like this:
define bla
set $conti=1
while $conti==1
set $u=*(int*)$address
if $u==<expected_value>
set $conti=0
else
cont
end
end
end
note the cont command in the else subclause; the
problem is that i dont know how to detect if the stop
was due to my watchpointed variable at $address, or
some other breakpoint/watchpoint occuring
simultaneously.
can i attach procedures to particular
watchpoints/breakpoints that get called when they are
triggered? apparently the only way to figure out what
type of break occurred is to have breaks/watchs to
modify dedicated variables
cheers
___________________________________________________________
100mb gratis, Antivirus y Antispam
Correo Yahoo!, el mejor correo web del mundo
http://correo.yahoo.com.ar
next reply other threads:[~2004-07-14 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 23:09 Charlls Quarra [this message]
2004-07-15 1:27 ` Daniel Jacobowitz
2004-07-15 6:42 ` 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=20040714230107.40234.qmail@web41813.mail.yahoo.com \
--to=charlls_quarra@yahoo.com.ar \
--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