This is the mail archive of the gdb-patches@sourceware.cygnus.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]

Delete sim/SIM_HAVE_BREAKPOINTS and gdb/SIM_HAS_BREAKPOINTS


Hello,

One of the target macros that keeps lurking in GDB is
SIM_HAS_BREAKPOINTS.  Checking the actual code, I've found that only the
d30v actually uses it.  (The d30v is a VLIW embedded processor).  Given
that the functionality provided by SIM_HAS_BREAKPOINTS can be
implemented using other more direct means I'd like to propose that the
macro be purged.

The idea behind the code (and sounds good in theory) was that the
simulator should administer its breakpoints directly. Unfortunatly,
reality got in the way, and several things conspired to ensure that it
was never widely adopted.  Of note are:

	o	as I mentioned, only one
		target adopted it in the end.

		Several other sim targets think
		that they are using the mechanism
		but a more careful examination of
		the source code reveals otherwize :-)

	o	turns out that equivalent
		functionality can be achieved
		by having GDB pass signals
		back to the simulator when
		an unknown breakpoint is
		encountered.

		It also turns out that providing
		this functionality is far more
		useful.

	o	It used the s/w breakpoint
		mechanism, just like GDB.

		If it had exploited the
		sim/common h/w breakpoint
		and watchpoint framework
		then I suspect it would
		be heavily used.

Any comments?

	Andrew

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