Method and apparatus for run-time memory access checking and memory leak detection of a multi-threaded program

Claim 3

The method of claim 1 wherein said MT safe debugger program maintains said memory status information in a multi-threaded safe manner by using synchronization primitives to lock-out concurrent accesses to it until said memory status is updated or checked for a current thread, after which time said accesses are unlocked.

Claim 4

The method of claim 1 wherein said checking for an error when said status information for said memory location accessed indicates an unallocated state is done on a per-thread basis.

Claim 5

The method of claim 1 comprising the additional step of reporting an error if said status information for said memory location accessed indicates an unallocated state.

Claim 6

The method of claim 4 wherein said reporting of an error when said status information for said memory location accessed indicates an unallocated state is done on a per-thread basis.

Claim 7

The method of claim 1 comprising the additional steps of: providing memory leak status information for memory locations in said memory, said memory leak status information indicating at least whether a memory location is in an inaccessible state or not, wherein said inaccessible state corresponds to a memory location which is in an allocated state but which is inaccessible in said multi-threaded target computer program, said memory leak status information being maintained by said MT safe debugger program; and under the control of said computer system, said MT safe debugger program checking said memory leak status information and reporting said memory locations designated as in said inaccessible state.

Claim 8

The method of claim 1 wherein said memory accesses may be either a read access or a write access and wherein said memory status information maintained by said MT safe debugger program comprises allocated states designated as read-only, write-only, and read or write access.

Claim 11

The method for memory leak checking of a multi-threaded target program of claim 8 having an additional step of reporting to a user said memory locations designated as in an inaccessible state.

Claim 12

A computer system for memory access checking of a multi-threaded target program, one or more central processing units (CPUs) and having program machine said computer system comprising: a memory; a clock; at least one central processing unit; a plurality of program machine instructions loaded into said memory; a multi-threaded operating system loaded into said memory; at least one I/O device for receiving inputs; at least one I/O device for sending outputs to; at least one of peripheral device; a multi-threaded safe ("MT safe") debugger program having memory access checking facilities, loaded into said memory and coupled to said multi-threaded operating system; a multi-threaded target program loaded into said memory under control of said MT safe debugger; one of said one or more CPUs for executing said multi-threaded operating system and said MT safe debugger to test said multi-threaded target program, said MT safe debugger having a first machine executable mechanism which provides memory status information for memory locations in said memory, said memory status information indicating at least whether a memory location is in an allocated state or in an unallocated state, wherein said allocated state corresponds to a memory location allocated by a computer program and said unallocated state corresponds to a memory location not allocated by said computer program, said status information being maintained by said MT safe debugger program during said test of said multi-threaded target program; and said MT safe debugger having a second machine executable mechanism which checks said memory status information for each memory location accessed by said multi-threaded target program.

Claim 13

A computer system for memory access checking of a multi-threaded target program, one or more central processing units (CPUs) and having program machine said computer system comprising: a memory; a clock; at least one central processing unit; a plurality of program machine instructions loaded into said memory; a multi-threaded operating system loaded into said memory; at least one I/O device for receiving inputs; at least one I/O device for sending outputs to; at least one of peripheral device; a multi-threaded safe ("MT safe") debugger program having memory access checking facilities, loaded into said memory and coupled to said multi-threaded operating system; a multi-threaded target program loaded into said memory under control of said MT safe debugger; one of said one or more CPUs for executing said multi-threaded operating system and said MT safe debugger to test said multi-threaded target program, said MT safe debugger having a first machine executable mechanism which provides memory status information for memory locations in said memory, said memory status information indicating at least whether a memory location is in an allocated state or in an unallocated state, wherein said allocated state corresponds to a memory location allocated by a computer program and said unallocated state corresponds to a memory location not allocated by said computer program, said status information being maintained by said MT safe debugger program during said test of said multi-threaded target program; and said MT safe debugger having a second machine executable mechanism which checks said memory status information for each memory location accessed by said multi-threaded target program.

Claim 14

The computer system of claim 10 further comprising a reporting mechanism for reporting of an error when said status information for said accessed memory locations are in an unallocated state.

Claim 15

The computer system of claim 10 wherein said checking for an error when said status information for said memory location accessed indicates an unallocated state is done on a per-thread basis.

Claim 16

The computer system of claim 11 wherein said reporting of an error when said status information for said memory location accessed indicates an unallocated state is done on a per-thread basis.

Claim 17

The computer system of claim 10 wherein said memory accesses may be either a read access or a write access and wherein said memory status information maintained by said MT safe debugger program comprises allocated states designated as read-only, write-only, and read or write access.

Claim 18

The computer system of claim 10 wherein said checking for an error if said status information for said memory location accessed indicates an unallocated state is done on a per-thread basis.

Claim 19

The computer system of claim 10 further comprising: a third machine executable mechanism coupled to said MT safe debugger which provides memory leak status information for memory locations in said memory, said memory leak status information indicating at least whether a memory location is in an inaccessible state or not wherein said inaccessible state corresponds to a memory location which is in an allocated state but which is inaccessible in said computer program, said memory leak status information being maintained by said MT safe debugger program; and a fourth machine executable mechanism coupled to said MT safe debugger which checks said memory leak status information.

Claim 20

The computer system of claim 16 further comprising a reporting mechanism for reporting said memory locations designated as in an inaccessible state.

Claim 21

A computer system, comprising: a memory; a clock; at least one central processing unit; a plurality of program machine instructions loaded into said memory; a multi-threaded operating system loaded into said memory; at least one I/O device for receiving inputs; at least one I/O device for sending outputs to; at least one peripheral device; a multi--threaded safe ("MT safe") debugger program having memory leak checking facilities, loaded into said memory and coupled to said multi-threaded operating system; a multi-threaded target program loaded into said memory under control of said MT safe debugger; one of said one or more CPUs for executing said multi-threaded operating system and said MT safe debugger to test said multi-threaded target program, said MT safe debugger having a first machine executable mechanism which provides memory leak status information for memory locations in said memory, said memory leak status information indicating at least whether a memory location is in an inaccessible state or not wherein said inaccessible state corresponds to a memory location which is in an allocated state but which is inaccessible in said computer program, said leak status information being maintained by said MT safe debugger program during said test of said multi-threaded target program; and said MT safe debugger having a second machine executable mechanism which checks said memory leak status information for each memory location accessed by said multi-threaded target program.

Claim 22

A computer system, comprising: a memory; a clock; at least one central processing unit; a plurality of program machine instructions loaded into said memory; a multi-threaded operating system loaded into said memory; at least one I/O device for receiving inputs; at least one I/O device for sending outputs to; at least one peripheral device; a multi--threaded safe ("MT safe") debugger program having memory leak checking facilities, loaded into said memory and coupled to said multi-threaded operating system; a multi-threaded target program loaded into said memory under control of said MT safe debugger; one of said one or more CPUs for executing said multi-threaded operating system and said MT safe debugger to test said multi-threaded target program, said MT safe debugger having a first machine executable mechanism which provides memory leak status information for memory locations in said memory, said memory leak status information indicating at least whether a memory location is in an inaccessible state or not wherein said inaccessible state corresponds to a memory location which is in an allocated state but which is inaccessible in said computer program, said leak status information being maintained by said MT safe debugger program during said test of said multi-threaded target program; and said MT safe debugger having a second machine executable mechanism which checks said memory leak status information for each memory location accessed by said multi-threaded target program.

Claim 23

The computer system of claim 18 wherein said second machine executable mechanism which checks said memory leak status information for each memory location accessed by said multi-threaded target program performs said checking on a per-thread basis.

Claim 24

The computer system of claim 18 further comprising a reporting mechanism for reporting of said memory locations which are designated as in an inaccessible state, said inaccessible locations designated as memory leaks.

Claim 25

The computer system of claim 20 wherein said reporting mechanism which reports said memory leak status information for each memory location accessed by said multi-threaded target program performs said reporting on a per-thread basis.

Claim 26

A debugger in a computer readable medium for providing a multithreaded safe ("MT safe") mechanism for run-time-checking ("RTC") a multi-threaded target program, said debugger operating in a computer system having a memory, a clock, one or more central processing units (CPUs), an I/O device for receiving inputs, an I/O device for sending outputs to, and at least one peripheral device, said debugger comprising: a first machine executable structure for maintaining status of memory locations in a computer system, said memory status information indicating at least whether a memory location is in an allocated state or in an unallocated state, wherein said allocated state corresponds to a memory location allocated by a computer program and said unallocated state corresponds to a memory location not allocated by said computer program, said status information being maintained by said MT safe mechanism during a test of said multi-threaded target program; and a second machine executable structure which checks said memory status information for each memory location accessed by said multi-threaded target program.

Claim 27

A debugger in a computer readable medium for providing a multithreaded safe ("MT safe") mechanism for run-time-checking ("RTC") a multi-threaded target program, said debugger operating in a computer system having a memory, a clock, one or more central processing units (CPUs), an I/O device for receiving inputs, an I/O device for sending outputs to, and at least one peripheral device, said debugger comprising: a first machine executable structure for maintaining status of memory locations in a computer system, said memory status information indicating at least whether a memory location is in an allocated state or in an unallocated state, wherein said allocated state corresponds to a memory location allocated by a computer program and said unallocated state corresponds to a memory location not allocated by said computer program, said status information being maintained by said MT safe mechanism during a test of said multi-threaded target program; and a second machine executable structure which checks said memory status information for each memory location accessed by said multi-threaded target program.

Claim 28

A debugger as articulated in claim 22 wherein said second machine executable structure performs said checks of said memory status information for each memory location accessed by said multi-threaded target program on a per-thread basis.

Claim 29

A debugger as articulated in claim 22 further comprising a reporting mechanism for reporting an error if said status information for said memory location accessed indicates an unallocated state, said second machine executable structure under control of said MT safe mechanism.

Claim 30

A debugger as articulated in claim 24 wherein said reporting mechanism performs said reporting of said memory status information for each memory location accessed by said multi-threaded target program on a per-thread basis.