Patent application number | Description | Published |
20120079459 | TRACING MULTIPLE THREADS VIA BREAKPOINTS - In an embodiment, a plurality of halted addresses of halted instructions are determined, at which execution of a plurality of threads of a program are halted. A respective next sequential instruction is computed, which is in the plurality of threads following the plurality of halted instructions. A respective next sequential breakpoint at the respective next sequential instruction in the plurality of threads is set. Execution of the plurality of threads is started after the setting the respective next sequential breakpoint. In response to the execution of each of the plurality of threads encountering the respective next sequential breakpoint and all of the plurality of threads halting, trace data is saved that describes the execution of each of the plurality of threads. | 03-29-2012 |
20120110553 | IMPLEMENTING A STEP-TYPE OPERATION DURING DEBUGGING OF CODE USING INTERNAL BREAKPOINTS - Debugging of code of a computer program is facilitated by implementing a step-type operation using internal breakpoints to ensure debugger control of the code. During a debugging session, a step-type operation is implemented by setting active internal breakpoints on every line of code of every routine currently on the call stack referenced by the processor and on entry points of the code being debugged, and subsequently leaving in place, upon completion of the step-type operation, active internal breakpoints. Subsequent to implementing the step-type operation any active internal breakpoints encountered during execution of one or more other operations of the code and deemed unnecessary to completion of the other operation(s) are disabled, and the location of any internal breakpoints disabled during execution of the one or more other operations are tracked in a data structure(s) for subsequent use in reestablishing needed internal breakpoints for implementation of another step-type operation. | 05-03-2012 |
20120110554 | STEP-TYPE OPERATION PROCESSING DURING DEBUGGING BY MACHINE INSTRUCTION STEPPING CONCURRENT WITH SETTING BREAKPOINTS - Debugging of code of a computer program is facilitated by implementing, during a debugging session, a step-type operation by machine instruction stepping through the code, and concurrent therewith, setting up breakpoints to perform the step-type operation. Responsive to the machine instruction stepping reaching a next debuggable line of code prior to completion of setup of breakpoints to perform the step-type operation, the machine instruction stepping is discontinued, and the setting up of breakpoints to perform the step-type operation is discontinued. Alternatively, responsive to completing setup of the breakpoints to perform the step-type operation prior to machine instruction stepping reaching the next debuggable line of code, the machine instruction stepping is discontinued, and the code is executed to perform the step-type operation using the set breakpoints. | 05-03-2012 |
20120110555 | VARYING REMOVAL OF INTERNAL BREAKPOINTS DURING DEBUGGING OF CODE - Debugging of code of a computer program is facilitated by having a plurality of internal breakpoints associated with lines of code previously set by a processor, during a debugging session, while implementing one or more step-type operations. During execution of another operation, internal breakpoints are disabled as encountered and deemed unnecessary to completion of the another operation. A count of a number of interrupts of one or more interrupt-types experienced during execution of the another operation is maintained, and responsive to the count exceeding a threshold, the disabling is varied to remove at least N internal breakpoints responsive to encountering an internal breakpoint during execution of the another operation deemed unnecessary to completion of the another operation, where N≧2. | 05-03-2012 |
20130142196 | DISTRIBUTING FUNCTIONS IN A DISTRIBUTED AND EMBEDDED ENVIRONMENT - The different switch modules making up a distributed virtual switch may route configuration commands for hardware resources to different modules within the distributed switch using a distribution and routing layer. At least one of the switch modules maintains a routing table that defines which switch modules are responsible for which hardware resources. The switch module uses the routing tables to forward the commands on the distribution and routing layer to the responsible switch module which then ensures that the relevant hardware resources are configured. | 06-06-2013 |
20150229524 | CONSTRUCTING AND VERIFYING SWITCH FABRIC CABLING SCHEMES - A distributed network switch includes multiple switch modules connected by one or more physical cables. One switch module may determine which connector port of a remote switch module is connected by physical cable based on information received from the remote switch module, including link identifiers, and further based on a physical topology predetermined about the type of remote switch module. | 08-13-2015 |
20150229529 | CONSTRUCTING AND VERIFYING SWITCH FABRIC CABLING SCHEMES - A distributed network switch includes multiple switch modules connected by one or more physical cables. One switch module may determine which connector port of a remote switch module is connected by physical cable based on information received from the remote switch module, including link identifiers, and further based on a physical topology predetermined about the type of remote switch module. | 08-13-2015 |