Appeal 2007-0506
Application 09/998,511
Nishimura allows a user to set a breakpoint on an object basis or at a
desired location in an object (col. 14, ll. 55-65).
"An 'object-type breakpoint' is used to break the execution of a user-
specified object when an operation is performed on the object . . . ."
(Col. 14, ll. 65-67). When the user sets an object-type breakpoint, the
breakpoint setting section 16 sets a breakpoint in all of the public functions
of the class and of the indirect base classes (col. 15, ll. 12-17), where "all
[of] the derived (higher level) classes, including the base class of a class, the
base class of the base class, and so forth, are called indirect base classes"
(col. 2, ll. 33-37). "By setting breakpoints in all those functions, the user can
determine whether a break occurs when one of those functions is called."
(Col. 15, ll. 17-19.)
"[A]n 'address-type breakpoint' is used to break the execution of an
object when control reaches a user-specified location in a user-specified
object (that is, at a location in a particular member function or in a particular
location in an inherited member function)." (Col. 15, ll. 1-5.) By setting the
breakpoint only in a function or at an address within the object whose
breakpoint is to be checked, the breakpoint does not break execution unless
control reaches the corresponding address, increasing debugging efficiency
(col. 15, ll. 6-11).
Anticipation
Claim 1 requires "halting execution of the object-oriented computer
program during debugging in response to reaching an implementation of the
5
Page: Previous 1 2 3 4 5 6 7 8 9 10 Next
Last modified: September 9, 2013