From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18115 invoked by alias); 21 Mar 2011 14:39:14 -0000 Received: (qmail 18022 invoked by uid 22791); 21 Mar 2011 14:39:13 -0000 X-SWARE-Spam-Status: No, hits=-6.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Mar 2011 14:39:02 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p2LEd013003878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Mar 2011 10:39:00 -0400 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p2LEcwr4002040; Mon, 21 Mar 2011 10:38:59 -0400 From: Phil Muldoon To: Kevin Pouget Cc: gdb@sourceware.org Subject: Re: GDB Python API: stop/continue after breakpoint References: Reply-to: pmuldoon@redhat.com X-URL: http://www.redhat.com Date: Mon, 21 Mar 2011 14:39:00 -0000 In-Reply-To: (Kevin Pouget's message of "Mon, 21 Mar 2011 10:19:00 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-03/txt/msg00109.txt.bz2 Kevin Pouget writes: > cool, that's working perfectly now ! > > just one thing: > >> >> >> [Switching to Thread 0x7ffff7de1700 (LWP 2417)] >> >> Breakpoint -9, rdb_notify_event () at replay_db.c:11 >> 11 void rdb_notify_event() {} > > is there any way / woudn't it be nice to have the ability to disable > the breakpoint hit outputs? at least for the 'internal' breakpoints, > which shouldn't be visible to the user ? You can set the breakpoint to silent: (gdb) python b = gdb.Breakpoint("hello.c:5", internal=True) (gdb) run Breakpoint -1, main () at /home/pmuldoon/hello.c:5 5 printf("Hello world!\n"); (gdb) py b.silent = True (gdb) run (gdb) list (gdb) where #0 main () at /home/pmuldoon/hello.c:5 There might be a case for setting the breakpoint to 'silent' in the breakpoint constructor: python b = gdb.Breakpoint("hello.c:5", internal=True, silent=True) or just making internal breakpoints silent by default. I'll implement either. What do you think? Cheers, Phil