# US 8,752,023 B2 · System, method and program product for executing a debugger > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,752,023 B2 - Document ID: US8752023B2 - Status: Granted - Kind: B2 - Application number: 13/571,236 - Filed: 2012-08-09 - Published: 2012-11-29 - Granted: 2014-06-10 - Earliest claimed: 2008-01-09 - Assignees: International Business Machines Corporation - Applicants: Nir Golan; Aviad Zlotnick - Inventors: Nir Golan; Aviad Zlotnick - Web page: https://patentgrep.com/patent/US8752023B2 ## CPC - G06F 11/362: Debugging of software - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method for controlling a debugger, the method includes: determining whether to execute a certain breakpoint of the debugger in view of certain breakpoint conditional information and in view of at least one previous visit, during the execution of the debugger, to at least one other breakpoint of the debugger; and selectively executing the certain breakpoint in response to the determination. ## Claims ### Claim 1 A method for controlling a debugger, the method comprising: using a processor of a system to associate breakpoint identification information to breakpoints of a debugger; determining whether to execute a certain breakpoint of the debugger in view of certain breakpoint conditional information and in view of at least one previous visit, during the execution of the debugger, to at least one other breakpoint of the debugger using the processor of the system; and selectively executing the certain breakpoint in response to the determination. ### Claim 2 (depends on 1) The method according to claim 1 wherein the determining is preceded by receiving a certain breakpoint conditional attribute that conditions an execution of the certain breakpoint by at least one previous visit, during the execution of the debugger, to the at least one other breakpoint. ### Claim 3 (depends on 1) The method according to claim 1 wherein the determining is responsive to a certain breakpoint conditional attribute that is a debugger primitive. ### Claim 4 (depends on 1) The method according to claim 1 wherein the determining is preceded by defining a certain breakpoint conditional attribute that conditions an execution of the certain breakpoint by at least one previous visit, during the execution of the debugger, to the at least one other breakpoint. ### Claim 5 (depends on 1) The method according to claim 1 wherein the determining is further responsive to at least one previous visit to the certain breakpoint. ### Claim 6 (depends on 1) The method according to claim 1 further comprising generating breakpoint visit indicators that comprise breakpoint identification information and number of visits information. ### Claim 7 (depends on 1) The method according to claim 1 further comprising limiting a number of visits that can affect the determining to a predefined number. ### Claim 8 (depends on 1) The method according to claim 1 further comprising limiting a number of breakpoints that once visited affect the determining. ### Claim 9 A program product comprising a non-transitory computer usable medium including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to: determine whether to execute a certain breakpoint of a debugger in view of certain breakpoint conditional information and in view of at least one previous visit, during the execution of the debugger, to at least one other breakpoint of the debugger; and execute the certain breakpoint in response to the determination, wherein the computer readable program when executed on a computer causes the computer to associate breakpoint identification information to breakpoints of the debugger. ### Claim 10 (depends on 9) The program product according to claim 9, wherein the computer readable program when executed on a computer causes the computer to determine whether to execute a certain breakpoint of the debugger in view of a certain breakpoint conditional attribute that is a debugger primitive. ### Claim 11 (depends on 9) The program product according to claim 9, wherein the computer readable program when executed on a computer causes the computer to receive a certain breakpoint conditional attribute that conditions an execution of the certain breakpoint by at least one previous visit, during the execution of the debugger, to the at least one other breakpoint. ### Claim 12 (depends on 9) The program product according to claim 9, wherein the computer readable program when executed on a computer causes the computer to define a certain breakpoint conditional attribute that conditions an execution of the certain breakpoint by at least one previous visit, during the execution of the debugger, to the at least one other breakpoint. ### Claim 13 (depends on 9) The program product according to claim 9, wherein the computer readable program when executed on a computer causes the computer to determine whether to execute a certain breakpoint of the debugger in view of at least one previous visit to the certain breakpoint. ### Claim 14 (depends on 9) The program product according to claim 9, wherein the computer readable program when executed on a computer causes the computer to generate breakpoint visit indicators that comprise breakpoint identification information and number of visits information. ### Claim 15 (depends on 9) The program product according to claim 9, wherein the computer readable program when executed on a computer causes the computer to limit a number of visits that can affect the determining to a predefined number. ### Claim 16 (depends on 9) The program product according to claim 9, wherein the computer readable program when executed on a computer causes the computer to limit a number of breakpoints that once visited affect the determining.