Abstract: A method and electronic device are provided for maintaining a message store having a plurality of messages includes maintaining at the electronic device a client bookmark indicating a point in the message store up to which the content of the message store maintained at the electronic device is known to be complete, and a maximum message identifier (ID) indicating the largest message identifier of the plurality of messages of the message store that the electronic device has received, sending to a server a sync request message for the message store, the sync request message including the client bookmark in response to determining at least one of the client bookmark and the maximum message ID do not match, and the electronic device connecting with the server after a period of being disconnected.

Abstract: A method and electronic device are provided for maintaining a message store having a plurality of messages includes maintaining at the electronic device a client bookmark indicating a point in the message store up to which the content of the message store maintained at the electronic device is known to be complete, and a maximum message identifier (ID) indicating the largest message identifier of the plurality of messages of the message store that the electronic device has received, sending to a server a sync request message for the message store, the sync request message including the client bookmark in response to determining at least one of the client bookmark and the maximum message ID do not match, and the electronic device connecting with the server after a period of being disconnected.

Abstract: A large portion of software bugs are related to hangs. Analyzing and diagnosing hang-related bugs involves capturing data from a hung program and extracting attributes from the captured data. Extracting attributes from the capture data provides a scheme to determine relevant characteristics of the hang. Moreover, the extracted attributes may be compared to known issues and, based on that comparison, a bug may be classified as known or unknown. Alternatively, triage may be performed on the client computing device in order to determine the potential cause of the hang event. Once the potential cause of the hang event has been determined, troubleshooting steps may be performed on the client computing device to quarantine it. Ultimately, if the hang-inducing bug is known, a user may be provided with a solution to the bug. Alternatively, if the bug is unknown, implementations of the invention send the captured data to be analyzed and fixed by the software's provider.

Abstract: A vertical can be a series of computer-executable instructions that, in response to an incident, collect information regarding that incident and transmit the information for analysis and possible helpful feedback to the user. A general purpose vertical can address types of incidents, such as crashes or hangs, across a variety of applications, while a custom vertical can be written to address application-specific incidents. Verticals can access underlying support mechanisms through an infrastructure, which can also enable applications to request that additional data be collected by the verticals, and set other preferences. Once the data is collected and transmitted, a vertical may receive feedback, that can be a request for additional information or feedback to the user. The feedback to the user can attempt to identify the incident and aid the user in recovering from it and avoiding it in the future.

Abstract: A large portion of software bugs are related to hangs. Analyzing and diagnosing hang-related bugs involves capturing data from a hung program and extracting attributes from the captured data. Extracting attributes from the capture data provides a scheme to determine relevant characteristics of the hang. Moreover, the extracted attributes may be compared to known issues and, based on that comparison, a bug may be classified as known or unknown. Alternatively, triage may be performed on the client computing device in order to determine the potential cause of the hang event. Once the potential cause of the hang event has been determined, troubleshooting steps may be performed on the client computing device to quarantine it. Ultimately, if the hang-inducing bug is known, a user may be provided with a solution to the bug. Alternatively, if the bug is unknown, implementations of the invention send the captured data to be analyzed and fixed by the software's provider.

Abstract: A system and method to facilitate communication between a user interface and an associated process is disclosed. A first thread is associated with the user interface and a second thread is associated with the process for implementing requests by the user interface. At least one state buffer is operable to store state data for controlling ownership to the state buffer by the first and second threads for communicating data between the first and second threads. The architecture may be used in connection with a debugging system, such as to facilitate responsive interaction between the GUI and the associated debugging system.

Abstract: A debugger can debug any of a plurality of debuggees. Each debuggee has a debugging type attribute selected from a plurality of debugging type attributes and representative of a type of debugging to be performed with respect to the debuggee. Each debuggee also has a processor attribute selected from a plurality of processor attributes and representative of a type of processor associated with the debuggee. The debugger is instantiated on a computer, and has an engine for performing debugging functions with respect to any of the plurality of debuggees. The engine includes a plurality of debugging type blocks, where each debugging type block supports at least one of the plurality of debugging type attributes, and a plurality of processor blocks, where each processor block supports at least one of the plurality of processor attributes.