From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-24349-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 32496 invoked by alias); 17 Feb 2006 20:08:19 -0000
Received: (qmail 32485 invoked by uid 22791); 17 Feb 2006 20:08:18 -0000
X-Spam-Check-By: sourceware.org
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)     by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 17 Feb 2006 20:08:17 +0000
Received: from drow by nevyn.them.org with local (Exim 4.54) 	id 1FABtm-0007xS-7x; Fri, 17 Feb 2006 15:08:14 -0500
Date: Fri, 17 Feb 2006 20:15:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: MI: reporting of multiple breakpoints
Message-ID: <20060217200814.GC30145@nevyn.them.org>
Mail-Followup-To: Eli Zaretskii <eliz@gnu.org>, 	Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
References: <dt4ofp$60k$1@sea.gmane.org> <20060217153211.GA21402@nevyn.them.org> <dt4r7g$h69$1@sea.gmane.org> <ulkw9hj1y.fsf@gnu.org> <20060217194426.GA28988@nevyn.them.org> <uek21hi3y.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <uek21hi3y.fsf@gnu.org>
User-Agent: Mutt/1.5.8i
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2006-02/txt/msg00209.txt.bz2

On Fri, Feb 17, 2006 at 09:59:13PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 17 Feb 2006 14:44:26 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
> > 
> > > Does anyone know why we return PRINT_SRC_AND_LOC for breakpoints?
> > 
> > That's how we get the source line printed when we stop, isn't it? 
> 
> Well, then perhaps the question is why does bpstat_print exits the
> loop when it sees PRINT_SRC_AND_LOC:
> 
>   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;
>     }

I've no idea.  I assume it's to show the first relevant breakpoint
message, and we might need to redesign the code and interface a bit if
we wanted more than one to be presented.

-- 
Daniel Jacobowitz
CodeSourcery