From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22491 invoked by alias); 30 Sep 2010 14:41:47 -0000 Received: (qmail 22470 invoked by uid 22791); 30 Sep 2010 14:41:46 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Sep 2010 14:41:41 +0000 Received: (qmail 14512 invoked from network); 30 Sep 2010 14:41:40 -0000 Received: from unknown (HELO caradoc.them.org) (dan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 30 Sep 2010 14:41:40 -0000 Date: Thu, 30 Sep 2010 16:41:00 -0000 From: Daniel Jacobowitz To: Phil Muldoon Cc: gdb-patches@sourceware.org Subject: Re: [patch] Add visible flag to breakpoints. Message-ID: <20100930144132.GA15652@caradoc.them.org> Mail-Followup-To: Phil Muldoon , gdb-patches@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-09/txt/msg00511.txt.bz2 On Thu, Sep 30, 2010 at 03:02:14PM +0100, Phil Muldoon wrote: > This is part of a larger effort to improve the Python breakpoint support > within GDB. One of the use-cases we have in Python is for a command to > set (maybe a large) number of breakpoints to catch predefined > behavior. However we do not want this to impact the usability or > readability of the existing 'info breakpoints' output. This patch fixes > that by allowing breakpoints to become invisible to the user. How does this interact with GDB-internal breakpoints (those with negative numbers)? If you didn't need to switch visibility at runtime, you could just create these as internal. -- Daniel Jacobowitz CodeSourcery