From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2219 invoked by alias); 15 Apr 2002 20:03:46 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2198 invoked from network); 15 Apr 2002 20:03:44 -0000 Received: from unknown (HELO neon-gw.transmeta.com) (63.209.4.196) by sources.redhat.com with SMTP; 15 Apr 2002 20:03:44 -0000 Received: (from root@localhost) by neon-gw.transmeta.com (8.9.3/8.9.3) id NAA31416 for ; Mon, 15 Apr 2002 13:03:40 -0700 Received: from mailhost.transmeta.com(10.1.1.15) by neon-gw.transmeta.com via smap (V2.1) id xma031403; Mon, 15 Apr 02 13:03:20 -0700 Received: from casey.transmeta.com (casey.transmeta.com [10.10.25.22]) by deepthought.transmeta.com (8.11.6/8.11.6) with ESMTP id g3FK3NN15106 for ; Mon, 15 Apr 2002 13:03:23 -0700 (PDT) Received: (from dje@localhost) by casey.transmeta.com (8.9.3/8.7.3) id NAA11126; Mon, 15 Apr 2002 13:03:23 -0700 Date: Mon, 15 Apr 2002 13:03:00 -0000 Message-Id: <200204152003.NAA11126@casey.transmeta.com> X-Authentication-Warning: casey.transmeta.com: dje set sender to dje@casey.transmeta.com using -f From: Doug Evans To: gdb@sources.redhat.com Subject: does bpstat_print stop printing prematurely? X-SW-Source: 2002-04/txt/msg00258.txt.bz2 Does bpstat_print stop printing prematurely? I think it does. for (; bs; bs = bs->next) { val = print_bp_stop_message (bs); if (val == PRINT_SRC_ONLY || val == PRINT_SRC_AND_LOC || val == PRINT_NOTHING) return val; } What if there is 1 breakpoint that triggers and two watchpoints? As a user, whenever execution stops I'd kinda like to know which of all of my active watchpoints triggered without having to manually examine each one. Things are even more confusing if gdb prints some but not all of the triggering watchpoints. Example: Suppose the `bs' arg to bpstat_print contains a watchpoint, a pc breakpoint, and another watchpoint, in that order. Currently bpstat_print will print the first watchpoint and the pc breakpoint but not the second watchpoint. Blech. I'll file a pr unless something can rationalize the current behaviour.