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: Sun, 07 Apr 2002 12:16:22 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
> 
> What would it take to replace DECR_PC_AFTER_BREAK with a read_pc() 
> function that determines the stop address from the i386 hardware 
> registers and other state information?

How would that help to solve this specific problem?  The original
problem happened on i386 as well, right?  So at best, you'd be pushing
the ``rat's nest'' from GDB application level to x86-specific parts of
GDB, where there still will be need to decide what kind of breakpoint
to reports to the application level.

Or am I missing something?

In general, it strikes me that breakpoint.c's design goes against what
you propose: it defines an API where GDB queries the target about the
status of all the known break/watchpoints, and then decides what
happened based on what the target reports.  You seem to suggest a
different strategy: let the target tell GDB what happened.  While
certainly a viable idea, it sounds like a major redesign of a central
GDB facility, no?


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