Google Inc.

Sun Microsystems, Inc.

Timesys Corporation

Tymesys Corporation

Peter Cadwell Dibble

Scott D Robbins

Pratik Solanki

David S Hardin

Gregory Bollella

Ashish G Karkare

C Douglass Locke

Benjamin M Brosgol

Embodiments relate to systems, devices, and computer-implemented methods for creating a loadable image and using the loadable image for restarting an application. The method can include starting, by a computing device, initialization of the application, and identifying upon initialization of the application, a plurality of resources associated with the application. The method can further include determining checkpoints associated with the plurality of resources. In addition, the method can include creating an optimized image corresponding to the application based on the checkpoints and an optimization of an application image, and storing the optimized image in a memory. Further, the method can include restarting the application by replacing a current process image with a new process image, and updating the new process image with one or more elements of the optimized image.

Systems, devices, and methods for capturing information, creating loadable images, and providing for restarts in a computer system

Various implementations for verifying that a user device is being operated by a person are described. In some implementations, a method includes receiving a challenge request. The method selects two or more first images from a first image category and one or more second images from one or more second image categories, which are distinct from the first image category. The method sends a challenge to the user device for presentation to the person. The challenge includes a challenge parameter and data describing the two or more first images and the one or more second images. The method receives a challenge response from the user device describing a user selection of at least one image from among the two or more first images and the one or more second images and determines a result of the challenge based on the challenge response and the challenge parameter.

Image-based challenge-response testing

The invention relates to optimizing software code execution during state transitions. The system handles changes in execution context using differential rule checking techniques. For instance, when a thread executing in a data processing system changes state, its new state may be subject to different rules than its previous state. To enforce these rules, the thread may be associated with software code that causes certain restrictions, such as memory restrictions, to be applied to the thread. In an interpretive environment, this can be implemented by detecting a state transition in an active thread, and responding to the state transition by associating the thread with a dispatch table that reflects its state change. The dispatch table may cause the thread to be associated with code that enforces those restrictions. In one example, different dispatch tables can be provided, each table reflecting a different state of a thread, and each causing a thread to be subject to different restrictions. In another example, the same dispatch table can be rewritten to accommodate the changed state of the thread.

Multiple code sets for multiple execution contexts

A technique for implementing a data processor to determine if an exception has been thrown. Specifically, the technique may be used in an interpretive environment where a table known as a bytecode (upcode) dispatch table is used. The dispatch table contains addresses for code that implements each bytecode. When the interpreter executes normally, these addresses point to the basic target machine code for executing each bytecode. However, when an Asynchrounously Interrupted Exception (AIE) is thrown, then the dispatch table is repopulated so that all byte codes point to routines that can handle the exception. These may point to a routine, such as an athrow, that has been extended to handle the special case of the AIE. Alternatively, the rewritten table can point to a routine that is specifically written to handle the firing of an AIE. The table contents are restored to their prior state once the exception handling is complete. The scheme may also be implemented non-rewriting of the table if a thread is in a non-Asynchronous Transfer of Control (to defer ATC) deferred state.

Techniques for exception handling by rewriting dispatch table elements

An invention is provided for a synchronous transfer of control. An asynchronous interrupt exception is received, and in response, the value of a reference counter is determined. The value of the reference counter is based on the execution of synchronized code. Generally, the reference counter is initialized to a predetermined number, and altered based on the execution of synchronized code. When the asynchronous interrupt exception is received, the method is asynchronously interrupted when the value of the reference counter is equal to the predetermined number.

Growing community of inventors

Bethel Park, PA, United States of America

Peter Cadwell Dibble