From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb@sources.redhat.com
Subject: catchpoint - bptype
Date: Mon, 28 Apr 2008 18:13:00 -0000 [thread overview]
Message-ID: <fv4m61$9ul$1@ger.gmane.org> (raw)
Hello,
I need some input on the bptype enum, and catchpoint treatment:
Right now we internally treat some of them as bp_breakpoint and some as special bp_catch_*. Catchpoints "catch" and "throw" are treated as bp_breakpoint while others are treated as special types. For example "fork" is bp_catch_fork.
I see that bp_catch_catch and bp_catch_trhow were removed in Dec. 2007 and this confuses me a bit: what is the intention? To get rid of all bp_catch_*?
Since bptype is used to give more specific detail about a breakpoint it makes sense to have bp_catch_catch and bp_catch_throw there. It would also make those two catchpoints first-class citizens again.
Thoughts?
Thanks,
Aleksandar Ristovski
QNX Software Systems
next reply other threads:[~2008-04-28 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 18:13 Aleksandar Ristovski [this message]
2008-04-28 18:22 ` Joel Brobecker
2008-04-28 20:51 ` Aleksandar Ristovski
2008-04-28 20:09 ` Aleksandar Ristovski
2008-04-28 21:08 ` Daniel Jacobowitz
2008-04-29 17:05 ` Aleksandar Ristovski
2008-04-29 17:49 ` Daniel Jacobowitz
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='fv4m61$9ul$1@ger.gmane.org' \
--to=aristovski@qnx.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