# US 2012/0084760 A1 · Transactional debugger for a transactional memory system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0084760 A1
- Document ID: US20120084760A1
- Status: Published application
- Kind: A1
- Application number: 13/323,921
- Filed: 2011-12-13
- Published: 2012-04-05
- Earliest claimed: 2007-06-19
- Assignees: Microsoft Corporation
- Inventors: Martin Taillefer
- Web page: https://patentgrep.com/patent/US20120084760A1

## CPC

- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Various technologies and techniques are disclosed for providing a debugger for programs running under a transactional memory system. When running a particular program using the debugger, the system detects when a conflict occurs on at least one conflictpoint that was set in the particular program. A graphical user interface is provided that displays information related to the detected conflict. The graphical user interface can display transactional state and/or other details independently of a conflict. A conflictpoint can be assigned to one or more regions of source code in one or more transactions in the particular program. A conflictpoint can also be assigned to a particular variable in the particular program. When running the particular program in a debug mode, execution is stopped if a conflict occurs on any of the conflictpoints.

## Claims

### Claim 1

A computer storage medium having computer-executable instructions for causing a computer to perform steps comprising:
providing a transactional debugger application for debugging programs running under a transactional memory system;
using the transactional debugger application, detecting an occurrence of conflict on a conflictpoint set in at least one program running under the transactional memory system, wherein the conflict is between transactions;
because of the detected conflict, stopping execution of the at least one program running under the transactional memory system; and
displaying information related to the detected conflict occurrence.

### Claim 2 (depends on 1)

The computer storage medium of claim 1, wherein the information displayed includes details about all pending transactions in the program.

### Claim 3 (depends on 1)

The computer storage medium of claim 1, wherein the information displayed includes details about all pending transactions for a particular code segment.

### Claim 4 (depends on 1)

The computer storage medium of claim 1, wherein the information displayed includes information related to a nested child of the at least one program.

### Claim 5 (depends on 1)

The computer storage medium of claim 1, wherein the information displayed includes one or more visual indicators of the conflict.

### Claim 6 (depends on 1)

The computer storage medium of claim 1, wherein execution of the program is stopped when the conflict is detected.

### Claim 7 (depends on 1)

The computer storage medium of claim 1, wherein a user can assign the conflictpoint to a region of source code in a transaction.

### Claim 8 (depends on 1)

The computer storage medium of claim 1, wherein a user can assign the conflictpoint to a particular variable in the program.

### Claim 9 (depends on 1)

The computer storage medium of claim 1, wherein a user can customize settings for the conflictpoint that specify when the conflictpoint should be detected.

### Claim 10

A method for debugging transactions using conflictpoints on regions of code comprising the steps of:
using a processing unit, receiving input to assign a conflictpoint to a region of source code in a transaction in a particular program that runs under a transactional memory system;
when running the particular program in a debug mode, using the processing unit, stopping execution if a conflict occurs between transactions that are executing the region of source code; and
displaying information related to the conflict.

### Claim 11 (depends on 10)

The method of claim 10, wherein the region of code is a single line of code.

### Claim 12 (depends on 10)

The method of claim 10, wherein the region of code includes multiple lines of code.

### Claim 13 (depends on 10)

The method of claim 10, wherein the user can customize settings for the conflictpoint that specify when the conflictpoint should be detected.

### Claim 14 (depends on 10)

The method of claim 10, wherein the information includes a transactional state of each transaction involved in the conflict.

### Claim 15 (depends on 10)

The method of claim 10, wherein the transactional information includes a transactional state for all transactions pending at a time the conflict was detected.

### Claim 16 (depends on 10)

A computer-readable medium having computer-executable instructions for causing a computer to perform the steps recited in claim 10.

### Claim 17

A method for debugging transactions using conflictpoints on variables comprising the steps of:
using a processing unit, receiving input to assign a conflictpoint to a particular variable in a particular program that runs under a transactional memory system; and
when running the particular program in a debug mode, using the processing unit, stopping execution if accesses to the particular variable induce a conflict.

### Claim 18 (depends on 17)

The method of claim 17, further comprising:
displaying information related to the conflict, wherein the information displayed includes details about all pending transactions in the program.

### Claim 19 (depends on 17)

A computer-readable medium having computer-executable instructions for causing a computer to perform the steps recited in claim 17.

### Claim 20 (depends on 17)

The method of claim 17, wherein a user can customize settings for the conflictpoint that specify when the conflictpoint should be detected.
