| Patent application number | Description | Published |
|---|
| 20080275877 | METHOD AND SYSTEM FOR VARIABLE KEYWORD PROCESSING BASED ON CONTENT DATES ON A WEB PAGE - A method for modifying knowledge documents, includes: updating an index based on keyword weights, detecting a page that has not been indexed; parsing the page into structures; associating the structures with dates contained thereof; separating the dates on the page into one or more past and future dates; determining whether the page has undergone changes following the separating of dates; wherein in the event the page has not undergone changes the one or more future dates are checked to determine if one or more of the future dates have become additional past dates, and flagging the structures that contain the one or more additional past dates; and wherein during a keyword analysis of the page the structures associated with the one or more past dates and additional past dates are omitted when determining the keyword weights associated with the page. | 11-06-2008 |
| 20080313178 | DETERMINING SEARCHABLE CRITERIA OF NETWORK RESOURCES BASED ON COMMONALITY OF CONTENT - A method, article of manufacture, apparatus for determining keywords to be used by a search engine. In one embodiment, a list of hyperlinks contained in an electronic document is identified by a searching program. The searching program then accesses the resource content (e.g., HTML) from each resource pointed to by the hyperlinks. The resource content of each resource is examined to determine whether a commonality exists in a manner directed to identifying keywords for each resource. These keywords may then be used by a search engine to return more accurate results to user queries. | 12-18-2008 |
| 20090110287 | METHOD AND SYSTEM FOR DISPLAYING IMAGE BASED ON TEXT IN IMAGE - A method and a system for displaying an image based on texts in the image are provided. The method of the invention for displaying the image includes: a text extracting step, extracting text regions in the image to be displayed; a text occupancy amount calculating step, calculating occupancy amount of the text in said image; a comparing step, comparing the calculated occupancy amount with a predetermined threshold; a display step, displaying the image in real size of the image if said occupancy amount exceeds said predetermined threshold. It is achieved to display the image to the user in a manner of satisfying the viewing aim of the user, and unnecessary load of the computer system is avoided. | 04-30-2009 |
| 20090300112 | Effective Communication in Virtual Worlds - A method, computer program product and computer system for establishing an effective communication between two users in a virtual world, which includes measuring a communication capability for each of the users, and establishing a communication using a default type of communication, if a difference between the communication capabilities of the two users is not above a pre-determined threshold. The method, computer program product and computer system can further establish a communication using an alternate type of communication, if a difference is above the pre-determined threshold. | 12-03-2009 |
| 20090310785 | ENHANCED MESSAGE SECURITY - A secure messaging system and method includes receiving an encrypted message, the message having been encrypted using a token of a corresponding pervasive device; wirelessly verifying the presence of the pervasive device; and, if the presence can be verified, decrypting the message using the token. The verification step can include the steps of establishing a wireless link with the pervasive device; and, querying the pervasive device over the wireless link. The establishing step can include the step of establishing a Bluetooth link with the pervasive device. Furthermore, the querying step can include the step of requesting geographic coordinates which locate the pervasive device. | 12-17-2009 |
| 20090319725 | Methods, Systems and Computer Program Products for Detection of Frequent Improper Removals of and Changing Writing Policies to Prevent Data Loss in Memory Sticks - Methods, system and computer program products for detection of frequent improper removals of and changing writing policies to prevent data loss in memory sticks. Exemplary embodiments include a method including detecting insertions of the memory stick, detecting removals of the memory stick, tracking a number of times the memory stick has been docked when removed, tracking a number of times the memory stick has been undocked when removed, determining a removal ratio of times the memory has been removed when docked to the number of times the memory stick has been removed when undocked, comparing the removal ratio to a predetermined threshold, caching writes and directory updates, and committing the writes and directory updates to the memory stick when the removal ratio is below the predetermined threshold and, flushing all writes and updates to the memory stick when in the removal ratio is equal to or above the predetermined threshold. | 12-24-2009 |
| 20090320001 | SYSTEM, METHOD AND PROGRAM PRODUCT FOR MONITORING CHANGES TO DATA WITHIN A CRITICAL SECTION OF A THREADED PROGRAM - A method, system and program product for monitoring changes to a variable within a critical section of a threaded program. The method includes establishing, using a debugging tool, a watch for monitoring changes to a variable that occur outside of the critical section and executing a portion of the threaded program with a debugger. Further, the method includes determining, using the tool, whether or not a thread has executed a start breakpoint set for the critical section, if the thread has executed the start breakpoint set, determining whether or not the thread has executed an end breakpoint set for the critical section, and if the thread has not executed the end breakpoint set, displaying any watches triggered responsive to updates to the variable that occur outside of the critical section, such that, only updates to the variable that occur outside of the critical section will trigger the displaying. | 12-24-2009 |
| 20100005249 | Finding the Source Statement of the Definition of a Storage Location - In an embodiment, an identifier of a storage location that is accessed by a program is received. While execution of the program is halted at a halted statement, a first source statement is determined that must have stored to the storage location. The program comprises the halted statement and the first source statement, and the halted statement is different than the first source statement. The first source statement is presented, in response to the determination. In an embodiment, while execution of the program is halted at the halted statement, a second source statement is determined that might have stored to the storage location, and the second source statement is presented. | 01-07-2010 |
| 20100020085 | METHOD FOR AVATAR WANDERING IN A COMPUTER BASED INTERACTIVE ENVIRONMENT - A method for avatar wandering in a computer based interactive environment including for each avatar within a range of a current avatar, obtaining profiles of a user represented by the avatar, for each profile of the user represented by the avatar that has a same profile type as a profile of a user represented by the current avatar, comparing the profiles for matching data, computing a match score for the avatar based on the matching data, and moving the current avatar toward the avatar that has a greatest match score. | 01-28-2010 |
| 20100037152 | Presenting and Filtering Objects in a Virtual World - Embodiments of the invention provide techniques for filtering and presenting elements of an immersive virtual environment. The elements may be filtered according to importance to the user, based on user-specified importance of each element, the number and type of past interactions with the elements, and the like. Further, the filtering may be performed on the basis of the user's preference for density of element presentation. The user may then be presented with a view of the virtual world in which elements having a higher degree of interest to the user are highlighted visually, and in which elements having a lesser degree of interest to the user are made partially transparent or invisible. | 02-11-2010 |
| 20100064253 | Providing Users With Location Information Within a Virtual World - Embodiments of the invention provide techniques for providing information describing locations to users of an immersive virtual environment. In one embodiment, patterns of locations visited by various users of the virtual environment may be stored in a searchable data structure(s). Further, characteristics of the location visits may be used to determine whether a given location visit was favorable for each user. Subsequently, locations visited by a current user may be matched to one of the stored patterns of locations. The matching pattern may then be used to provide favorability information describing other locations available to the current user. The favorability information may be presented to the user as graphical indications visible within the user's view of the virtual environment. | 03-11-2010 |
| 20100076970 | Providing Location Information Within a Virtual World - Embodiments of the invention provide techniques for providing information describing locations to users of an immersive virtual environment. In one embodiment, patterns of locations visited by various users of the virtual environment may be stored in a searchable data structure(s). Further, characteristics of the location visits may be used to determine whether a given location visit was favorable for each user. Subsequently, locations visited by a current user may be matched to one of the stored patterns of locations. The matching pattern may then be used to provide favorability information describing other locations available to the current user. The favorability information may be presented to the user as graphical indications visible within the user's view of the virtual environment. | 03-25-2010 |
| 20100180214 | Predatory Behavior Detection and Alert in Virtual Worlds Based on Spatial and Temporal Criteria - Embodiments of the invention provide techniques for protecting a user from being followed by an avatar within an immersive virtual environment. To detect a following avatar, any avatars within a specified range of the user may be identified. Historical data may then be examined to determine if any of the identified avatars has been in the same recent virtual locations as the user. In order to rule out coincidental movements, the likelihood of both avatars being in the same places at the same time may be evaluated. Further, the following avatar may be tested by transporting the user to another location, and then monitoring to determine whether the following avatar also transports to the same location. Upon confirming that the following avatar is actually following the user, avoidance actions may be performed in order to avoid the following avatar. | 07-15-2010 |
| 20100180215 | Detecting Avatar Following in a Virtual Environment - Embodiments of the invention provide techniques for protecting a user from being followed by an avatar within an immersive virtual environment. To detect a following avatar, any avatars within a specified range of the user may be identified. Historical data may then be examined to determine if any of the identified avatars has been in the same recent virtual locations as the user. In order to rule out coincidental movements, the likelihood of both avatars being in the same places at the same time may be evaluated. Further, the following avatar may be tested by transporting the user to another location, and then monitoring to determine whether the following avatar also transports to the same location. Upon confirming that the following avatar is actually following the user, avoidance actions may be performed in order to avoid the following avatar. | 07-15-2010 |
| 20100242026 | ENHANCED THREAD STEPPING - Embodiments of the invention provide debugging techniques for multithreaded programs. For example, a debugger may reduce the time required to release inactive threads that hold resources needed by an active thread. For example, if a timer expires before a line of code finishes executing, the debugger assumes that the active thread requires a resource locked by an inactive thread and releases other threads. During subsequent execution of the line of code, the debugger reduces the timer length of the timer. In doing so, inactive threads are released sooner, thereby reducing the wait time a user experiences when debugging lines of code. | 09-23-2010 |
| 20100306744 | Debugger With Audiation - A method and computer program product are provided for audiating the occurrence of debugger events within a software debugger. The method begins by assigning a sound characteristic to a debugger event occurring within a software program under debug. Next, the audiation of the sound characteristic associated with the event is optimized to maximize performance of the debugger. Finally, the optimized sound characteristic associated with the event is played upon the occurrence of the event. | 12-02-2010 |
| 20110302651 | VERIFICATION OF A SEGMENTED PROGRAM ON A PARALLEL PROCESSING COMPUTING SYSTEM - Embodiments of the invention provide a method, apparatus, and program product to verify a program that includes a plurality of sections with a computing system that is configured to process a plurality of threads of execution. The method comprises verifying and executing a first section of the program utilizing a first thread of execution in response to activation of the program and determining a second section of the program to execute subsequent to the first section. The method further comprises verifying the second section utilizing a second thread of execution in parallel with the execution of the first section. Another embodiment of the invention provides a method of compiling program that includes program code by grouping the program code into sections based upon the execution time of the program code and based upon which program code is most commonly executed. | 12-08-2011 |
| 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 |
| 20120084758 | Collaborative Software Debugging In A Distributed System With Client-Specific Variable Evaluation - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving, by the debug server from the debug clients asynchronously during a debug session of the debuggee, a plurality of application-level messages; routing, by the message router in accordance with an application-level message passing protocol, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger to the debug clients with application-level messages routed to the back-end debugger; and returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results. | 04-05-2012 |
| 20120096437 | STEP GRANULARITY SELECTION IN A SOFTWARE DEBUGGER - A debugger allows a programmer to select the granularity of a line step function. Using a debugger step statement, the programmer can specify line step, statement step, or automatic selection. When the user specifies line step in the debugger statement, the debugger functions in true line step mode, where a line of source code is executed for each step. When the user specifies statement step in the debugger statement, the debugger functions in statement step mode, where a statement is executed for each step. When the user specifies automatic selection in the debugger statement, the program is analyzed, and a decision regarding whether to use line step or statement step is made based on the characteristics of the program and based on user-specified selection criteria. In this manner the function of the debugger when line stepping can vary according to the programmer's needs. | 04-19-2012 |
| 20120102459 | Collaborative Software Debugging In A Distributed System With Stacked Event Group Management - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving, from the debug clients, application-level messages, including multiple requests to establish an event notification; routing the messages among the debug clients, debug administrator, and back-end debugger, including forwarding each request to the debug administrator, and forwarding only one of the requests to the back-end debugger; establishing one event notification; assigning, for each request, the event notification to an event group, each event group associated with one of the requesting debug clients; and returning client-specific debug results including sending, to each of the requesting debug clients, an event notification upon the back-end debugger encountering the event at the location in source code. | 04-26-2012 |
| 20120102460 | Collaborative Software Debugging In A Distributed System With Client-Specific Dynamic Breakpoints - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving application-level messages, including receiving, from a requesting debug client, a request to establish a dynamic breakpoint at location in source code; routing the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger, sending to the debug administrator an instruction to register the dynamic breakpoint, and sending to the back-end debugger a command to establish the dynamic breakpoint; establishing the dynamic breakpoint; registering the requesting debug client's dynamic breakpoint; and returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results. | 04-26-2012 |
| 20120102463 | Collaborative Software Debugging In A Distributed System With Multi-Member Variable Expansion - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving application-level messages, including a request from a requesting debug client to notify other debug clients of an expansion of a multi-member variable; routing the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger to the debug clients and distributing, to the other debug clients, a notification of the expansion of the multi-member variable; and returning to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results. | 04-26-2012 |
| 20120102464 | Collaborative Software Debugging In A Distributed System With Collaborative Step Over Operation - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving application-level messages including receiving, from a requesting debug client, a step over command that includes an instruction to ignore, during the step over command, events established by the requesting debug client; routing the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger and routing the step over command to the back-end debugger; performing the step over command, including ignoring the events established by the requesting debug client and processing any other events; and returning, to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results. | 04-26-2012 |
| 20120102465 | Collaborative Software Debugging In A Distributed System With Client-Specific Access Control - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving, by the debug server, a plurality of application-level messages, including receiving, from a session owner, a request to enable a predefined operational mode; enabling the predefined operational mode; routing, by the message router in accordance with an application-level message passing protocol and in accordance with the enabled predefined operational mode, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger to the debug clients with application-level messages routed to the back-end debugger; and returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results. | 04-26-2012 |
| 20120102466 | Collaborative Software Debugging In A Distributed System With Graphic Representation Of Source Code Ownership Assignments - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving application-level messages including receiving a request to assign ownership of a portion of source code; routing the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including providing distributed control of the back-end debugger and forwarding, to the debug administrator, the request to assign ownership of the portion of source code; assigning ownership of the portion of the source code to the owning debug client; and returning, to the debug clients, client-specific debug results, including returning to the debug clients a description of the assignment of ownership to the owning debug client. | 04-26-2012 |
| 20120102467 | Collaborative Software Debugging In A Distributed System With Client-Specific Display Location Upon Event Notification - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes presenting a client-specific GUI; detecting user input including receiving a specification of display preferences specifying a preferred location at which to display source code of debuggee upon receipt of an event notification; receiving an event notification of an encountered event, the event notification specifying a location of the encountered event; and displaying client-specific debug results at the preferred location in source code without regard to the location of the encountered event. | 04-26-2012 |
| 20120110552 | PROTECTING BREAKPOINTS IN A SOFTWARE DEBUGGER - A debugger that includes a breakpoint protection mechanism that detects when the program being debugged has been modified to overwrite one or more instructions corresponding to existing breakpoints. When the debugger halts execution of a program being debugged, all of the set breakpoints are checked by determining whether the instruction corresponding to each breakpoint has changed. If any of the instructions corresponding to the breakpoints has changed, the corresponding breakpoint is removed. An optional warning may be provided to the user to inform the user of any removed breakpoints. | 05-03-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 |
| 20120110556 | HOLDING THREADS IN A SOFTWARE DEBUGGER - A debugger includes a thread holding mechanism that analyzes the code being executed by multiple threads, and delays holding each thread that is currently executing system code external to the program until the thread is no longer executing the system code external to the program, or until some threshold is exceeded. Delaying holding of a thread that is executing system code external to the program avoids potential conditions that could lock up the debugger. | 05-03-2012 |
| 20120117541 | Collaborative Software Debugging In A Distributed System With Dynamically Displayed Chat Sessions - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving application-level messages, including receiving, a request to establish a chat session associated with a location in source code of the debuggee; routing the application-level messages among the debug clients, the debug administrator, and the back-end debugger; returning client-specific debug results, including sending, to the debug clients, a notification of an established chat session; and administering, by the message router, chat content for the established chat session among debug clients. Debug clients display the chat content in a chat box at the location in source code when the view of source code includes the location. | 05-10-2012 |
| 20120117542 | Collaborative Software Debugging In A Distributed System With Client-Specific Event Alerts - In a distributed system including a debug server and debug clients coupled for data communications through a network, where the debug server includes a debug administrator, message router, back-end debugger, and a debuggee, collaborative software debugging includes: presenting a client-specific GUI; detecting user input through the GUI, including user input specifying a location to establish an event; establishing a client-specific event alert to be invoked upon receipt of an event notification for the event; generating application-level messages, including a request to establish the event; sending application-level messages to the debug server, including the request; receiving client-specific debug results, including an event notification for the event; and displaying the client-specific debug results, including invoking the client-specific event alert responsive to the event notification, without invoking an alert by at least one of the other debug clients receiving the event notification. | 05-10-2012 |
| 20120117543 | Collaborative Software Debugging In A Distributed System With Client-Specific Display Of Local Variables - In a distributed system that includes a debug server and debug clients coupled for data communications through a network, collaborative software debugging includes presenting a client-specific GUI that includes a client-specific local variables pane; detecting user input including detecting, by at least one particular debug client, user input setting the client-specific local variables pane to display local variables of a stack frame associated with an active routine owned by the particular debug client; generating and sending to the debug server application-level messages; receiving client-specific debug results; and displaying the client-specific debug results, including: displaying, in the particular debug client's client-specific local variables pane, the local variables of the stack frame associated with the active routine owned by the particular debug client; and displaying, in another debug client's client-specific local variables pane, local variables of another stack frame. | 05-10-2012 |
| 20120159117 | DISPLAYING VALUES OF VARIABLES IN A FIRST THREAD MODIFIED BY ANOTHER THREAD - In an embodiment, an address watch is established on a memory address while the execution of a first thread of a program is halted. In response to a second thread modifying memory contents at the memory address, encountering the address watch and halting, a determination is made whether a first variable in the program that represents the memory address is displayed on a user interface for the first thread. If the first variable in the program that represents the memory address is displayed on the user interface for the first thread, the value of the first variable is read and displayed on the user interface of the first thread. | 06-21-2012 |
| 20120159451 | IDENTIFYING THREADS THAT ENCOUNTER AN INSTRUCTION AT WHICH ANOTHER THREAD IS HALTED - In an embodiment, execution of a first thread of a plurality of threads is halted at a first instruction. A subset of the plurality of threads is determined that execute the first instruction while the first thread is halted at the first instruction. Identifiers of the subset of the plurality of threads that execute the first instruction while the first thread is halted at the first instruction are presented via a user interface for the first thread. | 06-21-2012 |
| 20120159487 | IDENTIFYING THREADS THAT WAIT FOR A MUTEX - In an embodiment, a first thread of a plurality of threads of a program is halted. A subset of the plurality of threads are determined that are waiting for a mutex that is locked by the first thread while the first thread is halted. Identifiers of the subset of the plurality of threads are presented. The subset of the plurality of threads may have their execution directly blocked and/or indirectly blocked by a lock on the mutex by the first thread. In embodiment, the first thread is halted in response to the first thread encountering a breakpoint, and the subset of the plurality of threads do not halt in response to the first thread encountering the breakpoint. | 06-21-2012 |
| 20120210305 | Event Management In A Non-Stop Debugging Environment - Event management in a non-stop debugging environment that includes a debugger configured to debug a debuggee, the debuggee including a number of threads of execution, where encountering an event by one of threads stops execution of only the one thread without concurrently stopping execution of other threads and event management includes: encountering, by a first thread, an event that stops execution of the first thread; while execution of the first thread is stopped, encountering, by each of one or more other threads, an event stopping execution of the other thread; queuing, by the debugger, the events stopping execution of the other threads; receiving, by the debugger from a user, an indication to flush one or more events from the queue; and flushing, by the debugger, the one or more events from the queue. | 08-16-2012 |
| 20120222008 | Thread-Specific Event Management In A Non-Stop Debugging Environment - A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee. In the non-stop debugging environment, encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of the other threads. Thread-specific events may managed in the non-stop debug environment by identifying, by the debugger for a thread of execution of the debuggee not currently executing, a thread-specific event associated with the thread; removing, by the debugger, the thread-specific event for all threads of the debuggee; and upon the thread resuming execution, replacing, by the debugger, the thread-specific event. | 08-30-2012 |
| 20120266134 | Managing Thread Execution In A Non-Stop Debugging Environment - Managing thread execution in a non-stop debugging environment that includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads, and managing thread execution includes: setting, by the debugger responsive to one or more user requests, one or more threads of the debuggee for auto-resumption; encountering, by a thread of the debuggee, an event stopping execution of the thread; determining whether the thread is set for auto-resumption; if the thread is set for auto-resumption, resuming, by the debugger, execution of the thread automatically without user interaction; and if the thread is not set for auto-resumption, processing, by the debugger, the event stopping execution of the thread. | 10-18-2012 |
| 20120266138 | Event Management In A Non-Stop Debugging Environment - Event management in a non-stop debugging environment that includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads and event management includes: receiving, by the debugger, a user request to establish a dynamically disabled event that is disabled for all threads upon a stop in execution of any thread; establishing, by the debugger, the dynamically disabled event; identifying, by the debugger, a stop in execution of a particular thread; and disabling, by the debugger, the dynamically disabled event for all threads of the debuggee. | 10-18-2012 |
| 20120266139 | Thread-Specific Watch Event Administration In A Non-Stop Debugging Environment - A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of threads stops execution of only the one thread without concurrently stopping execution of other threads. In the non-stop debugging environment, thread-specific watch event administration includes holding from execution, by the debugger, a thread triggering a watch event; determining, by the debugger, whether the watch event was set for the thread triggering the watch event; if the watch event was set for the thread triggering the watch event, setting, by the debugger, the debug perspective of a GUI to the thread triggering the watch event; and, if the watch event was not set for the thread triggering the watch event: retrieving, by the debugger, watch event information from the thread triggering the watch event; and resuming, by the debugger without user interaction, execution of the thread triggering the watch event. | 10-18-2012 |
| 20120266140 | Impact Indication Of Thread-Specific Events In A Non-Stop Debugging Environment - A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads. In such a non-stop debug environment, impact indication of thread-specific events includes tracking, by the debugger, activity associated with a thread-specific event and displaying, by the debugger in a graphical user interface (GUI), an indication of thread-specific event impact in dependence upon the tracked activity. | 10-18-2012 |
| 20120272216 | Collaborative Software Debugging In A Distributed System With Variable-Specific Messages - In a distributed system that includes a debug server and debug clients coupled for communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes: receiving application-level messages, including receiving, from a requesting debug client, a request to establish a variable-specific message for a particular variable; routing the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including establishing the variable-specific message; and returning, to the debug clients, client-specific debug results, including: responsive to each request by a variable evaluating debug client to evaluate a variable and if a variable-specific message has been established for the variable to be evaluated, returning the content of the variable-specific message to be displayed in association with the variable in the variable evaluating debug client's client-specific GUI along with the evaluation of the variable. | 10-25-2012 |
| 20120272217 | Collaborative Software Debugging In A Distributed System With Execution Resumption On Consensus - In a distributed system that includes a debug server and debug clients coupled for data communications, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving a number of application-level messages including a request to resume execution of the debuggee; routing the messages by the message router, providing distributed control of the back-end debugger to the debug clients, including: polling one or more debug clients for approval to resume execution of the debuggee and resuming execution of the debuggee only if a number of debug clients providing approval to resume execution of the debuggee exceeds a predefined threshold, and returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results. | 10-25-2012 |
| 20120272218 | Collaborative Software Debugging In A Distributed System With Stacked Run-To-Cursor Commands - In a distributed system that includes a debug server and debug clients coupled for data communications, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving a number of application-level messages, including receiving from a requesting debug client a run-to-cursor command; routing the messages among the debug clients, the debug administrator, and the back-end debugger, including: sending, to debug clients, a request for approval to carry out the run-to-cursor command; receiving responses to the request; and commanding the back-end debugger to execute the debuggee to a cursor position of one of the debug clients only after receiving a predefined number of approvals; and returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results. | 10-25-2012 |
| 20120272219 | Collaborative Software Debugging In A Distributed System With Symbol Locking - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving, from the debug clients, application-level messages, including receiving, from a symbol locking debug client, a request to lock one or more symbols from value modification; routing, by the message router, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including: establishing a lock for each of the one or more symbols; and returning, to the debug clients, client-specific debug results including, returning, responsive to a request to modify a value of a locked symbol, an indication that the symbol is locked without modifying the value of the locked symbol as requested. | 10-25-2012 |
| 20120278790 | Collaborative Software Debugging In A Distributed System With Real-Time Variable Modification Indicators - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes: receiving, by the debug server from the debug clients asynchronously during a debug session of the debuggee, a plurality of application-level messages, receiving, from a requesting debug client, a request to notify other debug clients that the requesting debug client is presently modifying a value of a particular variable; routing, by the message router, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including distributing to the other debug clients a notification of the modification the value of the particular variable; and returning, to the debug clients, client-specific debug results. | 11-01-2012 |
| 20120296650 | SPEECH RECOGNITION SYSTEM FOR PROVIDING VOICE RECOGNITION SERVICES USING A CONVERSATIONAL LANGUAGE - Embodiments of the present invention provide a method, system and article of manufacture for adjusting a language model within a voice recognition system, based on text received from an external application. The external application may supply text representing the words of one participant to a text-based conversation. n such a case, changes may be made to a language model by analyzing the external text received from the external application. | 11-22-2012 |
| 20120317552 | User-Specific Software Debugging - User-specific software debugging with user-specific step commands that includes: receiving a command to step execution to a source code module associated with a user; identifying routines in a call stack associated with the user; inserting, for each identified routine, a breakpoint at each source code line of the routine; inserting, for each source code module associated with the user and not in the call stack, a breakpoint at an entry point of the source code module; and executing the debuggee until the debuggee encounters one of the inserted breakpoints thereby halting execution of the debuggee. User-specific debugging with user-specific DLL load processing modes including: receiving a selection of a user-specific DLL processing mode; upon loading a DLL, retrieving a user identification; determining whether the DLL is associated with the user; and processing the DLL in accordance with user-specific DLL processing mode only if the DLL is associated with the user. | 12-13-2012 |
| 20130007716 | Collaborative Software Debugging In A Distributed System With Private Debug Sessions - In a distributed system that includes a debug server and debug clients coupled for data communications through a data communications network, where the debug server includes a debug administrator, a message router, a back-end debugger, and a debuggee, collaborative software debugging includes receiving, by the debug server from the debug clients, application-level messages including receiving, from a requesting debug client, a request to establish a private debug session of the debuggee; routing, by the message router, the application-level messages among the debug clients, the debug administrator, and the back-end debugger, including forwarding, to the back-end debugger, the request to establish a private debug session of the debuggee; and; and returning, by the debug server to the debug clients in response to the application-level messages routed to the back-end debugger, client-specific debug results, including establishing the private debug session of the debuggee for the requesting debug client. | 01-03-2013 |
| 20130007717 | Integrating Compiler Warnings Into A Debug Session - Integrating compiler warnings into a debug session including: receiving, by a debugger for a debug session of a debuggee from a compiler, compiled source code for execution and compiler warning data describing one or more compiler warnings generated at compile time of the debuggee, each compiler warning resulting from a source code variable statement in the debuggee source code; receiving, by the debugger, a request to evaluate a variable; determining, from the compiler warning data, whether evaluating the variable is dependent upon a source code variable statement resulting in a compiler warning; and, if evaluating the variable is dependent upon a source code variable statement resulting in a compiler warning, returning, by the debugger responsive to the request along with a result of the evaluation, a compiler warning indicator. | 01-03-2013 |
| 20130007718 | Software Debugging With Execution Match Determinations - Software debugging including: inserting, by a compiler compiling source code into a debuggable program, a phantom breakpoint at one or more lines of source code; including in the program; executing the program including encountering phantom breakpoints and removing each encountered phantom breakpoint; creating, upon exiting execution, a copy of the program that includes only phantom breakpoints not encountered during execution; providing the copy to a debugger; identifying, by the debugger, source code lines of the copy that do not include a phantom breakpoint; inserting an executed phantom breakpoint at the identified lines of the copy; executing the copy of the debuggable program including removing encountered breakpoints; and, after exiting execution of the copy, determining whether execution of the copy matches the execution of the debuggable program including, determining that the executions do not match if any phantom breakpoints were removed from the copy or any executed phantom breakpoint remains in the copy. | 01-03-2013 |
| 20130019228 | Resuming A Prior Debug SessionAANM Bates; Cary L.AACI RochesterAAST MNAACO USAAGP Bates; Cary L. Rochester MN US - Inserting, at debuggee source code lines, a breakpoint and executing. For each breakpoint encounter until exiting: encountering and removing the breakpoint, incrementing a first counter value, and resuming execution. Exiting includes saving the first counter value, a state of the call stack, and an exit location. In a second debug session, preparing the debuggee to resume from the exit location. Inserting, at the debuggee source code lines, a breakpoint and executing the debuggee. For each breakpoint encounter until a second counter value matches the first: encountering and removing the breakpoint, incrementing the second counter value, and resuming execution. When the first and second counter values match: inserting an exit location breakpoint at the exit location, executing the debuggee until encountering the exit location breakpoint, and providing the user control to resume debugging from the exit location only if the present state of the call stack matches the saved state. | 01-17-2013 |
| 20130031534 | Software Development With Information Describing Preceding Execution Of A Debuggable Program - Software development with information describing preceding execution of a debuggable program includes receiving, by a debugger from a compiler, a copy of a debuggable program, the debuggable program including one or more phantom breakpoints not encountered during a previous execution of the debuggable program, each phantom breakpoint inserted at a separate line of source code, phantom breakpoints encountered in a previous execution of the debuggable program being removed during the previous execution and not included in the copy of the debuggable program; executing, by the debugger, the copy of the debuggable program; upon each encounter of a breakpoint, determining, by the debugger, whether the encountered breakpoint is a phantom breakpoint; and if the encountered breakpoint is a phantom breakpoint, issuing, by the debugger, a warning indicating a point of straying execution. | 01-31-2013 |
| 20130036410 | Real-Time Temperature Sensitive Machine Level Code Compilation And Execution - Methods, apparatuses, and computer program products for real-time temperature sensitive machine level code compilation and execution are provided. Embodiments include compiling and executing, by a just-in-time (JIT) compiler, machine level code; during execution of the machine level code, determining, by the JIT compiler, an execution temperature for the machine level code, including reading temperature measurements from one or more processor temperature sensors; based on the determined execution temperature, identifying, by the JIT compiler, a portion of the machine level code that, when executed, caused temperature measurements of one or more processor temperature sensors to exceed a predetermined threshold temperature; recompiling, by the JIT compiler, the machine level code including modifying the identified portion to generate a new execution temperature that is lower than the previously determined execution temperature; and executing, by the JIT compiler, the recompiled machine level code. | 02-07-2013 |
| 20130046952 | Administering Thermal Distribution Among Memory Modules With Call Stack Frame Size Management - Administering thermal distribution among memory modules in a computing system that includes temperature sensors, where each temperature sensor measures temperature of a memory module and thermal distribution is effected by: determining, in real-time by a user-level application in dependence upon the temperature measurements of the temperature sensors, whether a memory module is overheated; if a memory module is overheated and if a current call stack frame is stored on the overheated memory module, increasing, by the user-level application, a size of the current call stack frame to fill remaining available memory space on the overheated memory module, ensuring a subsequent call stack frame is stored on a different memory module. | 02-21-2013 |
| 20130047142 | Thermal-Aware Source Code Compilation - Thermal-aware source code compilation including: receiving, by a compiler, an identification of a target computing system, the identification of the target computing system specifying temperature sensors that measure temperature of a memory module; compiling the source code into an executable application including inserting in the executable application computer program instructions for thermal-aware execution, the computer program instructions, when executed on the target computing system, carry out the steps of: retrieving temperature measurements of one or more of the target computing system's temperature sensors; determining, in real-time in dependence upon the temperature measurements, whether a memory module is overheated; if a memory module is overheated, entering a thermal-aware execution state including, for each memory allocation in the executable application, allocating memory on a different memory module than the overheated memory module; and upon the temperature sensors indicating the memory module is no longer overheated, exiting the thermal-aware execution state. | 02-21-2013 |
| 20130061007 | GENERATING CODE THAT CALLS FUNCTIONS BASED ON TYPES OF MEMORY - In an embodiment, in response to reading a declaration of a function that specifies a name of the function and a type of memory on which the function operates, the name of the function, a pointer to the function, and the type are saved to a template. In response to reading a call statement that specifies the name of the function and an identifier of an object, first code is generated. The first code, when executed, reads the pointer to the function from a virtual function table pointed to by the object, finds an entry in the virtual function table that represents the function, and reads the pointer from the entry in the virtual function table. The call statement, when executed, requests a call of the function. Second code is generated that, when executed, calls the function using the pointer read from the virtual function table. | 03-07-2013 |
| 20130067136 | Administering Thermal Distribution Among Memory Modules Of A Computing System - A computing system includes a number of memory modules and temperature sensors. Each temperature sensor measures a temperature of a memory module. In such a computing system a garbage collector during garbage collection, determines whether a temperature measurement of a temperature sensor indicates that a memory module is overheated and, if a temperature measurement of a temperature sensor indicates a memory module is overheated, the garbage collector reallocates one or more active memory regions on the overheated memory module to a non-overheated memory module. Reallocating the active memory regions includes copying contents of the active memory regions from the overheated memory module to the non-overheated memory module. | 03-14-2013 |
| 20130067155 | Memory Type-Specific Access Control Of A Field Of A Record - A computing system includes computer memory of a number of different memory types. An application program compiled for execution on the computing system controls access to a field of a record in the computer memory of the computing system by defining a record that includes one or more fields, the one or more fields including a restricted field having a specification of restricted accessibility when the restricted field is allocated in a particular memory type; allocating an instance of the record in memory of the particular memory type; and denying each attempted access of the restricted field while the record is allocated in the particular memory type. | 03-14-2013 |
| 20130067438 | MANAGING THREAD EXECUTION IN A NON-STOP DEBUGGING ENVIRONMENT - Managing thread execution in a non-stop debugging environment that includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads, and managing thread execution includes: setting, by the debugger responsive to one or more user requests, one or more threads of the debuggee for auto-resumption; encountering, by a thread of the debuggee, an event stopping execution of the thread; determining whether the thread is set for auto-resumption; if the thread is set for auto-resumption, resuming, by the debugger, execution of the thread automatically without user interaction; and if the thread is not set for auto-resumption, processing, by the debugger, the event stopping execution of the thread. | 03-14-2013 |
| 20130074041 | THREAD-SPECIFIC EVENT MANAGEMENT IN A NON-STOP DEBUGGING ENVIRONMENT - A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee. In the non-stop debugging environment, encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of the other threads. Thread-specific events may managed in the non-stop debug environment by identifying, by the debugger for a thread of execution of the debuggee not currently executing, a thread-specific event associated with the thread; removing, by the debugger, the thread-specific event for all threads of the debuggee; and upon the thread resuming execution, replacing, by the debugger, the thread-specific event. | 03-21-2013 |
| 20130074044 | EVENT MANAGEMENT IN A NON-STOP DEBUGGING ENVIRONMENT - Event management in a non-stop debugging environment that includes a debugger configured to debug a debuggee, the debuggee including a number of threads of execution, where encountering an event by one of threads stops execution of only the one thread without concurrently stopping execution of other threads and event management includes: encountering, by a first thread, an event that stops execution of the first thread; while execution of the first thread is stopped, encountering, by each of one or more other threads, an event stopping execution of the other thread; queuing, by the debugger, the events stopping execution of the other threads; receiving, by the debugger from a user, an indication to flush one or more events from the queue; and flushing, by the debugger, the one or more events from the queue. | 03-21-2013 |
| 20130074045 | INTEGRATING COMPILER WARNINGS INTO A DEBUG SESSION - Integrating compiler warnings into a debug session including: receiving, by a debugger for a debug session of a debuggee from a compiler, compiled source code for execution and compiler warning data describing one or more compiler warnings generated at compile time of the debuggee, each compiler warning resulting from a source code variable statement in the debuggee source code; receiving, by the debugger, a request to evaluate a variable; determining, from the compiler warning data, whether evaluating the variable is dependent upon a source code variable statement resulting in a compiler warning; and, if evaluating the variable is dependent upon a source code variable statement resulting in a compiler warning, returning, by the debugger responsive to the request along with a result of the evaluation, a compiler warning indicator. | 03-21-2013 |
| 20130086555 | STEP GRANULARITY SELECTION IN A SOFTWARE DEBUGGER - A debugger allows a programmer to select the granularity of a line step function. Using a debugger step statement, the programmer can specify line step, statement step, or automatic selection. When the user specifies line step in the debugger statement, the debugger functions in true line step mode, where a line of source code is executed for each step. When the user specifies statement step in the debugger statement, the debugger functions in statement step mode, where a statement is executed for each step. When the user specifies automatic selection in the debugger statement, the program is analyzed, and a decision regarding whether to use line step or statement step is made based on the characteristics of the program and based on user-specified selection criteria. In this manner the function of the debugger when line stepping can vary according to the programmer's needs. | 04-04-2013 |
| 20130086559 | RESUMING A PRIOR DEBUG SESSION - Inserting, at debuggee source code lines, a breakpoint and executing. For each breakpoint encounter until exiting: encountering and removing the breakpoint, incrementing a first counter value, and resuming execution. Exiting includes saving the first counter value, a state of the call stack, and an exit location. In a second debug session, preparing the debuggee to resume from the exit location. Inserting, at the debuggee source code lines, a breakpoint and executing the debuggee. For each breakpoint encounter until a second counter value matches the first: encountering and removing the breakpoint, incrementing the second counter value, and resuming execution. When the first and second counter values match: inserting an exit location breakpoint at the exit location, executing the debuggee until encountering the exit location breakpoint, and providing the user control to resume debugging from the exit location only if the present state of the call stack matches the saved state. | 04-04-2013 |
| 20130097588 | HOLDING THREADS IN A SOFTWARE DEBUGGER - A debugger includes a thread holding mechanism that analyzes the code being executed by multiple threads, and delays holding each thread that is currently executing system code external to the program until the thread is no longer executing the system code external to the program, or until some threshold is exceeded. Delaying holding of a thread that is executing system code external to the program avoids potential conditions that could lock up the debugger. | 04-18-2013 |
| 20130097589 | EVENT MANAGEMENT IN A NON-STOP DEBUGGING ENVIRONMENT - Event management in a non-stop debugging environment that includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads and event management includes: receiving, by the debugger, a user request to establish a dynamically disabled event that is disabled for all threads upon a stop in execution of any thread; establishing, by the debugger, the dynamically disabled event; identifying, by the debugger, a stop in execution of a particular thread; and disabling, by the debugger, the dynamically disabled event for all threads of the debuggee. | 04-18-2013 |
| 20130097590 | IMPACT INDICATION OF THREAD-SPECIFIC EVENTS IN A NON-STOP DEBUGGING ENVIRONMENT - A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads. In such a non-stop debug environment, impact indication of thread-specific events includes tracking, by the debugger, activity associated with a thread-specific event and displaying, by the debugger in a graphical user interface (GUI), an indication of thread-specific event impact in dependence upon the tracked activity. | 04-18-2013 |
| 20130097591 | THREAD-SPECIFIC WATCH EVENT ADMINISTRATION IN A NON-STOP DEBUGGING ENVIRONMENT - A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of threads stops execution of only the one thread without concurrently stopping execution of other threads. In the non-stop debugging environment, thread-specific watch event administration includes holding from execution, by the debugger, a thread triggering a watch event; determining, by the debugger, whether the watch event was set for the thread triggering the watch event; if the watch event was set for the thread triggering the watch event, setting, by the debugger, the debug perspective of a GUI to the thread triggering the watch event; and, if the watch event was not set for the thread triggering the watch event: retrieving, by the debugger, watch event information from the thread triggering the watch event; and resuming, by the debugger without user interaction, execution of the thread triggering the watch event. | 04-18-2013 |
| 20130103885 | ADMINISTERING THERMAL DISTRIBUTION AMONG MEMORY MODULES OF A COMPUTING SYSTEM - A computing system includes a number of memory modules and temperature sensors. Each temperature sensor measures a temperature of a memory module. In such a computing system a garbage collector during garbage collection, determines whether a temperature measurement of a temperature sensor indicates that a memory module is overheated and, if a temperature measurement of a temperature sensor indicates a memory module is overheated, the garbage collector reallocates one or more active memory regions on the overheated memory module to a non-overheated memory module. Reallocating the active memory regions includes copying contents of the active memory regions from the overheated memory module to the non-overheated memory module. | 04-25-2013 |
| 20130103919 | ADMINISTERING THERMAL DISTRIBUTION AMONG MEMORY MODULES WITH CALL STACK FRAME SIZE MANAGEMENT - Administering thermal distribution among memory modules in a computing system that includes temperature sensors, where each temperature sensor measures temperature of a memory module and thermal distribution is effected by: determining, in real-time by a user-level application in dependence upon the temperature measurements of the temperature sensors, whether a memory module is overheated; if a memory module is overheated and if a current call stack frame is stored on the overheated memory module, increasing, by the user-level application, a size of the current call stack frame to fill remaining available memory space on the overheated memory module, ensuring a subsequent call stack frame is stored on a different memory module. | 04-25-2013 |
| 20130104108 | PROTECTING BREAKPOINTS IN A SOFTWARE DEBUGGER - A debugger that includes a breakpoint protection mechanism that detects when the program being debugged has been modified to overwrite one or more instructions corresponding to existing breakpoints. When the debugger halts execution of a program being debugged, all of the set breakpoints are checked by determining whether the instruction corresponding to each breakpoint has changed. If any of the instructions corresponding to the breakpoints has changed, the corresponding breakpoint is removed. An optional warning may be provided to the user to inform the user of any removed breakpoints. | 04-25-2013 |
| 20130104110 | THERMAL-AWARE SOURCE CODE COMPILATION - Thermal-aware source code compilation including: receiving, by a compiler, an identification of a target computing system, the identification of the target computing system specifying temperature sensors that measure temperature of a memory module; compiling the source code into an executable application including inserting in the executable application computer program instructions for thermal-aware execution, the computer program instructions, when executed on the target computing system, carry out the steps of: retrieving temperature measurements of one or more of the target computing system's temperature sensors; determining, in real-time in dependence upon the temperature measurements, whether a memory module is overheated; if a memory module is overheated, entering a thermal-aware execution state including, for each memory allocation in the executable application, allocating memory on a different memory module than the overheated memory module; and upon the temperature sensors indicating the memory module is no longer overheated, exiting the thermal-aware execution state. | 04-25-2013 |
| 20130104111 | REAL-TIME TEMPERATURE SENSITIVE MACHINE LEVEL CODE COMPILATION AND EXECUTION - Methods, apparatuses, and computer program products for real-time temperature sensitive machine level code compilation and execution are provided. Embodiments include compiling and executing, by a just-in-time (JIT) compiler, machine level code; during execution of the machine level code, determining, by the JIT compiler, an execution temperature for the machine level code, including reading temperature measurements from one or more processor temperature sensors; based on the determined execution temperature, identifying, by the JIT compiler, a portion of the machine level code that, when executed, caused temperature measurements of one or more processor temperature sensors to exceed a predetermined threshold temperature; recompiling, by the JIT compiler, the machine level code including modifying the identified portion to generate a new execution temperature that is lower than the previously determined execution temperature; and executing, by the JIT compiler, the recompiled machine level code. | 04-25-2013 |
| 20130110443 | GRANTING AUTHORITY IN RESPONSE TO DEFECT DETECTION | 05-02-2013 |
| 20130111448 | STEP GRANULARITY SELECTION IN A SOFTWARE DEBUGGER | 05-02-2013 |
| 20130152054 | SETTING BREAKPOINTS IN OPTIMIZED INSTRUCTIONS - A method, computer-readable storage medium, and computer system are provided. In an embodiment, in response to a command that requests setting a breakpoint at a line in a module, a determination is made whether a snapshot instruction exists before a machine instruction that implements a source statement at the line. If the snapshot instruction exists before the machine instruction that implements the source statement at the line, the breakpoint is set at the machine instruction that implements the source statement at the line. If the snapshot instruction does not exist before the machine instruction that implements the source statement at the line, the module is recompiled to add the snapshot instruction before the machine instruction that implements the source statement. | 06-13-2013 |
| 20130179731 | RECOVERING FROM A THREAD HANG - A method, computer-readable storage medium, and computer system are provided. In an embodiment, a detection is made that at least one thread, in a plurality of threads executing in a computer, has hung. A lock order of a plurality of locks used by the plurality of threads is determined. A determination is made that a first thread in the plurality of threads violates the lock order. After the determination that the first thread violates the lock order, the computer is restarted and the first thread that violates the lock order is scheduled on a reduced-speed processor. | 07-11-2013 |
| 20130263094 | SETTING BREAKPOINTS IN OPTIMIZED INSTRUCTIONS - A method, computer-readable storage medium, and computer system are provided. In an embodiment, a command is received that specifies a debug compile option and requests a compile of a module into object code. If the debug compile option specifies a first debug compile option, snapshot instructions are inserted immediately prior to each machine instruction in the object code at which a breakpoint was previously set. If the debug compile option specifies the first debug compile option, snapshot instructions are inserted immediately prior to each machine instruction in the object code that implements a control flow statement. | 10-03-2013 |
| 20130275947 | Compiling Source Code For Debugging With User Preferred Snapshot Locations - Compiling source code for debugging, including: receiving, by an optimizing compiler from a debugger, a user specification of preferred breakpoint locations in the source code; compiling, by the optimizing compiler, the source code, wherein compiling includes inserting a snapshot at one or more of the preferred breakpoint locations, and recording the location of each inserted snapshot; and providing, to the debugger by the optimizing compiler, the recorded locations of each inserted snapshot along with the compiled source code. | 10-17-2013 |
| 20130275948 | Compiling Source Code For Debugging With Expanded Snapshots - Debugging source code includes: tracking, by a debugger during a debug session, duration of user examination of source code locations; providing, by the debugger to an optimizing compiler, a source code examination profile specifying source code locations examined by the user during the debug session; and receiving, by the debugger from the optimizing compiler: compiled source code for debugging, the compiled source code comprising, at each of one or more source code locations specified in the source code examination profile: a snapshot before the source code of the source code location, followed by an expanded snapshot, the expanded snapshot including computer program instructions to enable, during a debug session, examination of variable values changing during execution of the source code at the source code location; and a recording of snapshot locations and expanded snapshot locations. | 10-17-2013 |
| 20130282835 | Filtering Message Posts in a Social Network - A social media mechanism processes messages for content that may require filtering of recipients of the message, and informs a user who drafted the message when the message might need to be filtered so it is not sent to all potential recipients of the message. The user may then select to send the message to all potential recipients, or to filter the recipients so the message is sent to less than all of the potential recipients. User profiles are created and maintained, and may include information that helps to determine when filtering of messages is desirable. Feedback buttons are also provided to provide feedback when a user does not like a message. | 10-24-2013 |
| 20130282841 | FILTERING MESSAGE POSTS IN A SOCIAL NETWORK - A social media mechanism processes messages for content that may require filtering of recipients of the message, and informs a user who drafted the message when the message might need to be filtered so it is not sent to all potential recipients of the message. The user may then select to send the message to all potential recipients, or to filter the recipients so the message is sent to less than all of the potential recipients. User profiles are created and maintained, and may include information that helps to determine when filtering of messages is desirable. Feedback buttons are also provided to provide feedback when a user does not like a message. | 10-24-2013 |
| 20130283243 | Compiling Source Code For Debugging With Variable Value Restoration Based On Debugging User Activity - Compiling source code includes receiving, by an optimizing compiler from a debugger, a variable value modification profile that specifies locations in the source code at which variable values modified during a debug session; compiling the source code, including: inserting snapshots at one or more of the locations in the source code at which variable values were modified, each snapshot including a breakpoint; and only for each snapshot at a location in the source code at which variable values were modified: inserting, between the breakpoint and remaining source code at the location of the snapshot, a module of computer program instructions that when executed retrieves a current value of a variable and stores the current value in a register; and recording the location of each inserted snapshot; and providing, to the debugger by the optimizing compiler, the recorded locations of each inserted snapshot along with the compiled source code. | 10-24-2013 |
| 20140007058 | DETERMINING SNAPSHOT PLACEMENT | 01-02-2014 |
| 20140033180 | ESTABLISHING CLOUD DEBUG BREAKPOINTS ASSIGNED TO USERS - In an embodiment, a cloud debug breakpoint, assigned to a first user, is established in a program at a first server in a cloud, wherein the first user selects the first server at which the program executes, from among servers in the cloud. The program at the servers in the cloud is executed, in response to requests from users. The program at the first server in the cloud is executed, in response to all requests from the first user to the program. If an identifier of a user that sent a request that the program was executing at a time that execution of the program at the first server reaches the cloud debug breakpoint matches an identifier of the first user assigned to the cloud debug breakpoint, the execution of the program is halted and control of a processor is given to a debugger. | 01-30-2014 |
| 20140074312 | DECREASING THE INTERNAL TEMPERATURE OF A COMPUTER IN RESPONSE TO CORROSION - In an embodiment, a current internal corrosion level at a current time is read from an internal corrosion sensor that is internal to a computer. An internal corrosion difference is calculated between the current internal corrosion level and a previous internal corrosion level. If the internal corrosion difference is more than a first threshold amount, a first action is performed that decreases an internal temperature of the computer. | 03-13-2014 |
| 20140075418 | REPLACING CONTIGUOUS BREAKPOINTS WITH CONTROL WORDS - In an embodiment, a first execution path in a program is determined that has been executed a largest number of times, as compared to at least one other path in the program. Swapped instructions are replaced in the program with breakpoints, wherein the swapped instructions are not on the first execution path. The breakpoints that are not on the first execution path and that are contiguous to each other are replaced in the program with a control word. | 03-13-2014 |
| 20140165041 | CRASH NOTIFICATION BETWEEN DEBUGGERS - Crash notification between debuggers, including: initiating, by a first debugger, a first debug session of a first application; detecting, by the first debugger, an error condition in the first application; determining, by the first debugger, whether any variables utilized by the first application are related to variables utilized by a second application, wherein the second application is being debugged in a second debug session by a second debugger; and communicating, by the first debugger to a second debugger, information associated with the error condition in the first application. | 06-12-2014 |
| 20140165042 | CRASH NOTIFICATION BETWEEN DEBUGGERS - Crash notification between debuggers, including: initiating, by a first debugger, a first debug session of a first application; detecting, by the first debugger, an error condition in the first application; determining, by the first debugger, whether any variables utilized by the first application are related to variables utilized by a second application, wherein the second application is being debugged in a second debug session by a second debugger; and communicating, by the first debugger to a second debugger, information associated with the error condition in the first application. | 06-12-2014 |
| 20140173140 | DETECTING FIRMWARE VERSION FOR AN INPUT/OUTPUT ADAPTER - An indication of a version of a firmware stored in an input/output adapter may be provided by a method that includes detecting whether a first pin is connected to an external circuit, detecting whether a second pin is unconnected to an external circuit, and causing the indication to be provided if the first pin is connected and the second pin is unconnected. The indication may be provided on the first pin. The first pin may include a power supply pin and the indication may be an average rate of power supplied to the input/output adapter. | 06-19-2014 |
| 20140201352 | SELECTIVE LOGGING OF NETWORK REQUESTS BASED ON SUBSETS OF THE PROGRAM THAT WERE EXECUTED - In an embodiment, in response to detecting a request by a program to access a network, if the request is the first time that the program requests to access the network, a subset of instructions is replaced in the program with supervisor call instructions. The supervisor call instructions cause respective interrupts of execution of the program. In response to each of the respective interrupts of execution of the program, the supervisor call instructions that caused the respective interrupts are replaced with the respective swapped instructions, and if a number of the respective interrupts of execution exceed a trap threshold, all remaining of the respective swapped instructions are stored to the program. | 07-17-2014 |
| 20140201718 | ANALYZING CONCURRENT DEBUGGING SESSIONS - Methods, apparatuses, and computer program products for analyzing concurrent debugging sessions are provided. Embodiments include a first debugger initiating a conditional breakpoint in a first debug session of a first application. The conditional breakpoint stops execution of the first application based on a condition of a value of a variable of a second application. Embodiments also include the first debugger requesting and receiving the value of the variable from a second debugger. Embodiments also include the first debugger evaluating the condition of the conditional breakpoint based on the received value of the variable. | 07-17-2014 |
| 20140201719 | ANALYZING CONCURRENT DEBUGGING SESSIONS - Methods, apparatuses, and computer program products for analyzing concurrent debugging sessions are provided. Embodiments include a first debugger initiating a conditional breakpoint in a first debug session of a first application. The conditional breakpoint stops execution of the first application based on a condition of a value of a variable of a second application. Embodiments also include the first debugger requesting and receiving the value of the variable from a second debugger. Embodiments also include the first debugger evaluating the condition of the conditional breakpoint based on the received value of the variable. | 07-17-2014 |
| 20140344784 | CONTROLLING ACCESS TO VARIABLES PROTECTED BY AN ALIAS DURING A DEBUGGING SESSION - According to embodiments of the invention, methods, computer readable storage medium, and a computer system for controlling access to variables protected by an alias are disclosed. The method may include monitoring, during a debug session, each attempt by a debugger to apply an operator to one or more variables protected by an alias. The method may also include determining whether to allow an application of an operator to a variable protected by an alias, wherein the determination is based at least in part on one or more rules. | 11-20-2014 |
| 20140344789 | STEP OVER OPERATION FOR MACHINE CODE FUNCTION CALLS - A method for implementing a step over operation by a debugger for an instruction in a routine includes receiving a step over command for an instruction and determining whether the instruction is a branch used for a function call. If the instruction is not a branch used for a function call, then the debugger treats the instruction as not a function call. If the instruction is a branch used for a function call, then the debugger determines whether the instruction is generated from source code. If the instruction is not generated from source code, then the debugger treats the instruction as not a function call. If the instruction is generated from source code, then the debugger treats the instruction as a function call. | 11-20-2014 |
| 20140344790 | EVALUATION OF STATEMENT-LEVEL BREAKPOINTS - A method for evaluating a breakpoint in a line of source code includes encountering the breakpoint and evaluating whether the breakpoint is at the start of the line. If the breakpoint is at the start of the line, then the debugger stops at the breakpoint and tracks the breakpoint. If the breakpoint is not at the start of the line, then the debugger evaluates whether the breakpoint is reached via a back branch. If the breakpoint is not at the start of the line and is reached via a back branch, then the debugger stops at the breakpoint and tracks the breakpoint. If the breakpoint is not at the start of the line and is not a back branch target, then the debugger passes the breakpoint and tracks the breakpoint. | 11-20-2014 |
| 20150033211 | PROGRAM DEBUGGER AND PROGRAM DEBUGGING - Debug information records associated with a weak function of the program are obtained. In response to receipt of an instruction of setting a breakpoint for the weak function in the program, breakpoint addresses corresponding one-to-one with each of the at least one debug information record are obtained. In response to the program being executed to a set breakpoint associated with the weak function, an address to which a program counter of the program points is obtained. A breakpoint address matching the address to which the program counter of the program points is obtained. A mark for the matching breakpoint address is set. In response to receipt of the instruction of setting a breakpoint for the weak function in the program again, a debug information record corresponding to the matching breakpoint address according to the at least one debug information record with the mark being set is obtained. | 01-29-2015 |
