This is the mail archive of the gdb-patches@sources.redhat.com 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: [RFA] Fix watchpoints when stepping over a breakpoint


> Date: Fri, 5 Apr 2002 10:54:16 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> > 
> > Isn't this a bit ad hoc?  I think the issue of doing TRT when both a
> > breakpoint and a watchpoint fire for the same instruction needs a more
> > general solution.  While ignoring breakpoints might be the Right Thing
> > in this particular case, I wonder what will be TRT in other cases?
> > 
> > Did you try to arrange for a normal breakpoint and a watchpoint on the
> > same instruction, and see what happens in that case, with and without
> > this patch?
> 
> Yes, I did - that's 'watch a.x' in gdb.c++/annota2.exp.  Without the
> patch it fails on i386-linux, with it it passes.

``Fails'' and ``passes'' are in the eyes of the beholder ;-)

I mean, I'm not even sure what is the ``right'' behavior in this case.
The annota2.exp test expects something very specific, but is that what
we want?  Perhaps GDB should say that both breakpoint and watchpoint
fired instead, or do something else?

I'd suggest to discuss this a bit, because otherwise I don't even know
what are the criteria for approving or rejecting the patch.  The mere
fact that the number of testsuite failures goes down is not enough,
IMHO.

> I don't really think it's any more ad-hoc than the trap_expected flag. 

Perhaps not, but that doesn't mean we should proliferate ad-hoc'ery.

More importantly, an introduction of a general-purpose mechanism to
ignore breakpoints is something that I consider to be dangerous,
because it is no longer limited to special situations such as
single-stepping.


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