Browse Prior Art Database

Structured enhanced breakpoit chain

IP.com Disclosure Number: IPCOM000244264D
Publication Date: 2015-Nov-27
Document File: 3 page(s) / 53K

Publishing Venue

The IP.com Prior Art Database

Abstract

Our idea is adding breakpoint rules and make the result of breakpoint state, which are hit or pass, be another's breakpoints' condition to enhance the flexibility of breakpoints chains. By using breakpoints rules and the ability of modifying other breakpoints, it can be easy to drive all breakpoints dynamically, even in multi-thread asynchronous cases.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Structured enhanced breakpoit chain

The relationship of breakpoint has to be changed manually and un-traceable, which make steps tedious, mechanical repeated and easy to go wrong. It is waste of time. In the meantime, it is hard to debug by setting single breakpoint in asynchronous situation.

Add breakpoint rule and make the result of breakpoint state, which are hit or pass, be another's breakpoint's condition to enhance the flexibility of breakpoint chains. By using breakpoint rules and the ability of modifying other breakpoint, it can be easy to drive all breakpoints dynamically, even in multi-thread asynchronous cases.

Mechanism:

1. Two new concept: point ruleand statepoint.

Statepoint is somehow familiar with normal breakpoint. The difference is, statepoint won't stop the program but will capture the memory if needed, including various in heap and current stackframe. Then it servers other breakpoints and statepoints by supplying them of various capture and condition result. Also,it can be upgrade to normal breakpoint.

Point rule is a metrics which contains various entries for breakpoints and statepoints. Each entry is compound of conditions and expressions. With conditions, expression would be able to do logical work and then modify other breakpoints and statepoints. This offers method to modifying breakpoints and statepoints automatically according to logical debug need.


2. Workflow, as an instance.

Assuming that there is a part of logic code, statepoint A is before breakpoint B. Note that A and B are in difference function, which means the stackframe differs, but in one thread.

============================= function alpha(){

int a....

...

..... <- where point A is
....

return

}

function beta(){ boolean b.... ...

1



Page 02 of 3

.....<- where point B is

....

return

} =============================

There are two point rule:

A point rule

=============================

if

point A is hit && a >0

then

active point B

end

=============================

B point rule

=============================

if

     point B is hit && point B is active && b is true then

stop the program at point B

end

=============================

According to rule A,its condition are A point is hit and a bigger than 0,its postive result is active the point B.

According to rule B,its condition are B point is active and b value is true,its postive result is stop the program at p...