From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/commit] Minor cleanup in breakpoint_thread_match
Date: Wed, 25 Mar 2009 18:00:00 -0000 [thread overview]
Message-ID: <20090325174911.GA9472@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
This is in preparation for adding handling of (Ada) task-specific
breakpoints in this routine. I could have just modified the condition
inside the loop, but it was getting too nested for my taste, making
the condition hard to read. So here's a cleanup that would provide
two improvements: readability, and computing of the ptid's thread-id
in a lazy way. Most of the time, at least for myself, I don't use
thread-specific breakpoints, so might as well not compute the thread ID.
Reference: http://www.sourceware.org/ml/gdb-patches/2009-03/msg00551.html
2009-03-25 Joel Brobecker <brobecker@adacore.com>
* breakpoint.c (breakpoint_thread_match): Split a large condition
into several smaller conditions. No behavior change.
Tested on x86_64-linux. I made this change in a pretty procedural and
mechanical way. But a second pair of eyes would be appreciated. Plus,
I'd like to know if others also prefer splitting this condition like
I did.
Thanks,
--
Joel
[-- Attachment #2: bp-cleanup.diff --]
[-- Type: text/x-diff, Size: 1273 bytes --]
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 7e50342..6b88601 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -1893,20 +1893,28 @@ int
breakpoint_thread_match (CORE_ADDR pc, ptid_t ptid)
{
const struct bp_location *bpt;
- int thread;
-
- thread = pid_to_thread_id (ptid);
-
+ /* The thread ID associated to PTID, computed lazily. */
+ int thread = -1;
+
ALL_BP_LOCATIONS (bpt)
{
if (bpt->loc_type != bp_loc_software_breakpoint
&& bpt->loc_type != bp_loc_hardware_breakpoint)
continue;
- if ((breakpoint_enabled (bpt->owner)
- || bpt->owner->enable_state == bp_permanent)
- && bpt->address == pc
- && (bpt->owner->thread == -1 || bpt->owner->thread == thread))
+ if (!breakpoint_enabled (bpt->owner)
+ && bpt->owner->enable_state != bp_permanent)
+ continue;
+
+ if (bpt->address != pc)
+ continue;
+
+ /* If this is a thread-specific breakpoint, and we haven't
+ computed the ptid's thread ID yet, compute it now. */
+ if (bpt->owner->thread != -1 && thread == -1)
+ thread = pid_to_thread_id (ptid);
+
+ if (bpt->owner->thread == -1 || bpt->owner->thread == thread)
{
if (overlay_debugging
&& section_is_overlay (bpt->section)
next reply other threads:[~2009-03-25 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 18:00 Joel Brobecker [this message]
2009-03-25 18:12 ` Joel Brobecker
2009-03-25 19:25 ` Pedro Alves
2009-03-25 22:12 ` Joel Brobecker
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=20090325174911.GA9472@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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