From: Andrew STUBBS <andrew.stubbs@st.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Disable thread specific breakpoints when thread dies
Date: Wed, 09 Nov 2005 19:06:00 -0000 [thread overview]
Message-ID: <43723446.7000903@st.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Hi,
The attached patch disables thread specific breakpoints if they are hit
(in another thread) after the specific thread has died.
The rationale is that, once dead, the thread in question can never come
back, and the breakpoint is then only a, potentially serious,
performance drain. Even if another thread can be created with that ID it
would not be appropriate to 'hit' the breakpoint.
The breakpoint is not deleted, only disabled. It may still be easily
re-enabled when the program is re-run.
Is this OK?
Andrew Stubbs
[-- Attachment #2: thread-break.patch --]
[-- Type: text/plain, Size: 1472 bytes --]
2005-11-09 Andrew Stubbs <andrew.stubbs@st.com>
* breakpoint.c (breakpoint_thread_match): Disable thread specific
breakpoints if we hit one after the thread has ceased to exist.
Index: src/gdb/breakpoint.c
===================================================================
--- src.orig/gdb/breakpoint.c 2005-05-29 04:13:17.000000000 +0100
+++ src/gdb/breakpoint.c 2005-11-01 13:49:40.000000000 +0000
@@ -1797,9 +1797,23 @@ breakpoint_thread_match (CORE_ADDR pc, p
if ((breakpoint_enabled (bpt->owner)
|| bpt->owner->enable_state == bp_permanent)
- && bpt->address == pc
- && (bpt->owner->thread == -1 || bpt->owner->thread == thread))
+ && bpt->address == pc)
{
+ /* Disable matched breakpoint if thread no longer exists: this
+ prevents other tasks from hitting the breakpoint and improves
+ performance. */
+ if ((bpt->owner->thread != -1) && (bpt->owner->thread != thread))
+ {
+ if (!target_thread_alive(thread_id_to_pid(bpt->owner->thread)))
+ {
+ printf_filtered (
+ "Breakpoint %d disabled as thread %d no longer alive.\n",
+ bpt->owner->number, bpt->owner->thread);
+ disable_breakpoint(bpt->owner);
+ }
+ continue; /* no need to consider this breakpoint any further */
+ }
+
if (overlay_debugging
&& section_is_overlay (bpt->section)
&& !section_is_mapped (bpt->section))
next reply other threads:[~2005-11-09 17:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 19:06 Andrew STUBBS [this message]
2005-11-13 21:13 ` Daniel Jacobowitz
2005-11-14 16:34 ` Andrew STUBBS
2005-11-14 17:11 ` Daniel Jacobowitz
2005-11-15 18:55 ` Andrew STUBBS
2005-11-16 16:23 ` Andrew STUBBS
2005-11-17 4:22 ` Daniel Jacobowitz
2005-11-17 16:34 ` Andrew STUBBS
2006-01-12 16:25 ` Andrew STUBBS
2006-01-13 4:19 ` Michael Snyder
2006-01-13 4:31 ` Daniel Jacobowitz
2006-01-12 16:27 ` Daniel Jacobowitz
2006-01-13 17:35 ` Andrew STUBBS
2006-01-13 20:11 ` Mark Kettenis
2006-01-14 15:46 ` Daniel Jacobowitz
2006-01-14 15:56 ` Mark Kettenis
2006-01-14 16:06 ` Daniel Jacobowitz
2006-01-16 12:57 ` Andrew STUBBS
2006-01-16 16:19 ` Andrew STUBBS
2006-01-20 14:56 ` Andrew STUBBS
2006-01-20 15:00 ` Daniel Jacobowitz
2006-01-20 22:41 ` Daniel Jacobowitz
2006-02-02 2:30 ` 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=43723446.7000903@st.com \
--to=andrew.stubbs@st.com \
--cc=gdb-patches@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