Cross address space thread control in a multithreaded environment
May 20, 2014. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesFacilitating return from an on-line debugging program to a target program breakpoint Photovoltaic cell array with light concentrating reflectors Operating system debugger System and method for controlling a highly parallel multiprocessor using an anarchy based scheduler for parallel execution thread scheduling Processor system for executing processes in parallel under multitask, control method of waiting for event of process Fast interrupt mechanism for interrupting processors in parallel in a multiprocessor system wherein processors are assigned process ID numbers Preemptive and non-preemptive scheduling and execution of program threads in a multitasking operating system Method apparatus for scheduling tasks in repeated iterations in a digital data processing system having multiple processors Method for debugging and testing the correctness of programs Dynamically established event monitors in event management services of a computer system InventorsApplicationNo. 192929 filed on 02/07/1994US Classes:718/100, TASK MANAGEMENT OR CONTROL717/131, Including analysis of program execution718/107Multitasking, time sharingExaminersPrimary: Kriess, Kevin A.Assistant: Toplu, Lucien U. Attorney, Agent or FirmInternational ClassesG06F 009/44G06F 011/00 AbstractA method of controlling the execution of the threads of a first application such as a user application from a second application such as a debugger application running in a different address space. After initializing trace mode for the user application, the debugger waits for an event to occur on one of the threads of the user application. Upon the occurrence of an event on one of the user application threads, an event handler obtains control of the thread execution. The event handler suspends execution of the remaining threads in the application, posts the debugger and then suspends its own execution. When the debugger application has completed its debugging operations, it posts the event handler, which resumes execution of the suspended threads and returns control to the thread on which the event occurred. If a subsequent event occurs on one thread while a previous event on another thread is being processed, the event handler for the subsequent event places it in a deferred event queue for deferred processing. Events consisting of breakpoints are redriven rather than being placed on the deferred queue. The debugger application may hold selected threads in a suspended state following resumption of the remaining threads by setting hold flags associated with those threads.Other References
| |
