From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12733 invoked by alias); 21 Apr 2011 08:49:36 -0000 Received: (qmail 12724 invoked by uid 22791); 21 Apr 2011 08:49:35 -0000 X-SWARE-Spam-Status: No, hits=-1.9 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, 21 Apr 2011 08:49:21 +0000 Received: (qmail 16880 invoked from network); 21 Apr 2011 08:49:20 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 21 Apr 2011 08:49:20 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [PATCH] Remove same-pc breakpoint notification for internal BPs Date: Thu, 21 Apr 2011 08:49:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.35-28-generic; KDE/4.6.2; x86_64; ; ) Cc: Kevin Pouget , Tom Tromey References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104210949.18831.pedro@codesourcery.com> X-IsSubscribed: yes 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: 2011-04/txt/msg00382.txt.bz2 On Thursday 21 April 2011 09:11:29, Kevin Pouget wrote: > + && b->number >= 0); Can you make those b->number > 0? `0' is used for momentary breakpoints, which aren't user visible either. (as principle, please re-paste the changelog when posting an updated patch, so we don't have go fish which patch goes with which changelog. It's practicaly 0 work to re-paste it, but it's not 0 work to look for it.) In all-stop/sync when the user has the prompt, no momentary breakpoint will be inserted (pending bugs), but in non-stop, it can happen: (gdb) next& (over a function call that never returns) ... (gdb) maint info breakpoints Num Type Disp Enb Address What -1 shlib events keep y 0x00007ffff7deba30 <_dl_debug_state> inf 1 breakpoint already hit 2 times ... 0 step resume keep y 0x0000000000400728 inf 1 thread 1 stop only in thread 1 (gdb) b *0x0000000000400728 Note: breakpoint 0 (thread 1) also set at pc 0x400728. Breakpoint 2 at 0x400728: file threads.c, line 51. (gdb) -- Pedro Alves