From: "Martin M. Hunt" <hunt@redhat.com>
To: Insight Mailing List <insight@sources.redhat.com>
Subject: [RFA] fix session breakpoints
Date: Sat, 13 Oct 2001 11:41:00 -0000 [thread overview]
Message-ID: <200112172247.OAA26694@cygnus.com> (raw)
I often use Insight to debug itself. After a few hundred times, things get a
bit slow as Insight sets a few hundred breakpoints on info_command and internal_error.
So here's a simple patch. It not only stops these breakpoints from accumulating but
will also eliminate them from .gdbtkinit.
--
Martin Hunt
GDB Engineer
Red Hat, Inc.
2001-12-17 Martin M. Hunt <hunt@redhat.com>
* library/session.tcl (SESSION_serialize_bps): Ignore
breakpoints set on internal_error and info_command because
these are set by .gdbinit and will be recreated by it.
Index: session.tcl
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/session.tcl,v
retrieving revision 1.9
diff -u -r1.9 session.tcl
--- session.tcl 2001/10/28 20:08:39 1.9
+++ session.tcl 2001/12/17 22:43:15
@@ -38,6 +38,13 @@
address type enabled disposition ignore_count command_list \
condition thread hit_count user_specification
+ # These breakpoints are set when debugging GDB with itself.
+ # Ignore them so they don't accumulate. They get set again
+ # by .gdbinit anyway.
+ if {$function == "internal_error" || $function == "info_command"} {
+ continue
+ }
+
switch -glob -- $type {
"breakpoint" -
"hw breakpoint" {
WARNING: multiple messages have this Message-ID
From: "Martin M. Hunt" <hunt@redhat.com>
To: Insight Mailing List <insight@sources.redhat.com>
Subject: [RFA] fix session breakpoints
Date: Mon, 17 Dec 2001 14:49:00 -0000 [thread overview]
Message-ID: <200112172247.OAA26694@cygnus.com> (raw)
Message-ID: <20011217144900.G7i1W4kXm0lc426wwOvZ6thwWLkLCOmTH_rqXHG-npA@z> (raw)
I often use Insight to debug itself. After a few hundred times, things get a
bit slow as Insight sets a few hundred breakpoints on info_command and internal_error.
So here's a simple patch. It not only stops these breakpoints from accumulating but
will also eliminate them from .gdbtkinit.
--
Martin Hunt
GDB Engineer
Red Hat, Inc.
2001-12-17 Martin M. Hunt <hunt@redhat.com>
* library/session.tcl (SESSION_serialize_bps): Ignore
breakpoints set on internal_error and info_command because
these are set by .gdbinit and will be recreated by it.
Index: session.tcl
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/session.tcl,v
retrieving revision 1.9
diff -u -r1.9 session.tcl
--- session.tcl 2001/10/28 20:08:39 1.9
+++ session.tcl 2001/12/17 22:43:15
@@ -38,6 +38,13 @@
address type enabled disposition ignore_count command_list \
condition thread hit_count user_specification
+ # These breakpoints are set when debugging GDB with itself.
+ # Ignore them so they don't accumulate. They get set again
+ # by .gdbinit anyway.
+ if {$function == "internal_error" || $function == "info_command"} {
+ continue
+ }
+
switch -glob -- $type {
"breakpoint" -
"hw breakpoint" {
next reply other threads:[~2001-12-17 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 11:41 Martin M. Hunt [this message]
2001-12-17 14:49 ` Martin M. Hunt
2002-01-02 12:42 Martin M. Hunt
2002-01-02 12:46 ` Tom Tromey
2002-01-02 12:48 ` Ian Roxborough
2002-01-02 18:14 ` Keith Seitz
2002-01-03 13:44 ` Martin M. Hunt
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=200112172247.OAA26694@cygnus.com \
--to=hunt@redhat.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).