From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2192 invoked by alias); 17 Dec 2001 22:49:22 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 1254 invoked from network); 17 Dec 2001 22:47:55 -0000 Message-Id: <200112172247.OAA26694@cygnus.com> Content-Type: text/plain; charset="iso-8859-1" From: "Martin M. Hunt" Organization: Red Hat Inc To: Insight Mailing List Subject: [RFA] fix session breakpoints Date: Sat, 13 Oct 2001 11:41:00 -0000 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SW-Source: 2001-q4/txt/msg00123.txt.bz2 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 * 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" { From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin M. Hunt" To: Insight Mailing List Subject: [RFA] fix session breakpoints Date: Mon, 17 Dec 2001 14:49:00 -0000 Message-ID: <200112172247.OAA26694@cygnus.com> X-SW-Source: 2001-q4/msg00424.html Message-ID: <20011217144900.G7i1W4kXm0lc426wwOvZ6thwWLkLCOmTH_rqXHG-npA@z> 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 * 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" {