This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MI: reporting of multiple breakpoints


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]