Re: [RFC] PR 15075 dprintf interferes with "next"

[Yao Qi <yao@codesourcery.com>]

On 04/24/2013 07:59 AM, Hui Zhu wrote:
> 2013-04-23  Yao Qi<yao@codesourcery.com>
> 	    Hui Zhu<hui@codesourcery.com>
>
> 	PR gdb/15075
         ^^^^^^^^^^^^ "PR breakpoints/15075"

>
> 	* breakpoint.c (bpstat_stop_status): Call b->ops->after_cond.
> 	(update_dprintf_command_list): Don't append "continue" command
> 	to the command of dprintf breakpoint.
> 	(base_breakpoint_after_cond): New.
> 	(base_breakpoint_ops): Add base_breakpoint_after_cond.
> 	(dprintf_after_cond): New.
> 	(initialize_breakpoint_ops): Set dprintf_after_cond.
> 	* breakpoint.h (breakpoint_ops): Add after_cond.
>
> 2013-04-23  Hui Zhu<hui@codesourcery.com>
>
> 	PR gdb/15075
>
> 	* gdb.base/dprintf.exp: Remove "continue" from "info breakpoint"
> 	test.
We also need to stop checking "continue" in 
gdb.mi/mi-breakpoint-changed.exp also, as what patch [1] does.  B.T.W, 
why don't you add gdb.base/pr15075.[c,exp] from patch [1]?

-- 
Yao (齐尧)

[1] http://sourceware.org/ml/gdb-patches/2013-02/msg00736.html