This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI: reporting of multiple breakpoints
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Vladimir Prus <ghost at cs dot msu dot su>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 17 Feb 2006 21:29:04 +0200
- Subject: Re: MI: reporting of multiple breakpoints
- References: <dt4ofp$60k$1@sea.gmane.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Fri, 17 Feb 2006 18:01:13 +0300
>
> It seems that for stop on multiple breakpoints, MI reports only one:
>
> (gdb)
> -break-insert main
> ^done,bkpt={number="1",type="breakpoint".....
> (gdb)
> -break-insert main
> ^done,bkpt={number="2",type="breakpoint"......
> (gdb)
> -exec-run
> ^running
> (gdb)
> *stopped,reason="breakpoint-hit",bkptno="1",thread-id="1",frame={...}
>
> Is this a bug, or by design?
I think it's a bug. I don't see any reason not to report all the
breakpoints. As Daniel says, this is not limited to MI. (You will
see in "info breakpoints" that GDB does know that both breakpoints
triggered, it just doesn't print them both.)