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: Ctrl+C when a watchpoint is set gdb


On Tue, Nov 06, 2007 at 06:32:04PM -0800, Siva Velusamy wrote:
> However, the function bpstat_explains_signal is defined as follows:
> 
> breakpoint.h:547
> /* Nonzero if a signal that we got in wait() was due to circumstances
>    explained by the BS.  */
> /* Currently that is true if we have hit a breakpoint, or if there is
>    a watchpoint enabled.  */
> #define bpstat_explains_signal(bs) ((bs) != NULL)
> 
> Since there is a watchpoint defined, this ends up evaluating to true,
> even though this is a trap signal caused by Ctrl+C. Eventually, this
> leads to keep_going(ecs) being called.

You shouldn't be getting to the call to bpstat_explains_signal at all.
Is your remote stub returning the wrong signal for C-c?  It should be
TARGET_SIGNAL_INT, not TARGET_SIGNAL_TRAP.

-- 
Daniel Jacobowitz
CodeSourcery


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