105 results about "Managed code" patented technology

A system and method, useful in tracing program execution, for serializing data, such as an object data, into consistent, structured (e.g., XML) output. A serializer processes an object's data, and for each set of data, records the object's data in a structured (e.g., XML) format that reflects the object's current state. Nodes corresponding to fields and properties of the object are nested in the structure. Simple types define nodes with the current data value associated with the tag. More complex types including arrays, collections, dictionaries and exceptions are stored as individual members of a type, with any complex members further broken down into sub-nodes. Object data including custom collections, dictionaries, non-public fields and properties and properties with only get-accessor are serialized. The resulting output, such as in an XML formatted structure, is easy to read by humans, and is easily processed, such as for automated analysis purposes.

Described is a system and method by which an auxiliary computing device having an auxiliary display platform that displays information corresponding to data that originated on the main computer system may be extended by a device manufacturer. Extended hardware is added to the device, such as a radio receiver and/or an audio decoder. The auxiliary display platform is layered and extensible at each layer, and includes an extensible hardware abstraction layer that is extensible to support extended hardware if needed, and a driver layer that is extensible by adding driver code for the extended hardware. A runtime layer is also extensible to support the extended hardware as needed, as are libraries, the auxiliary shell program and other managed code. The client API is also extensible to allow applications on the main computer system to communicate with extended hardware via the device runtime layer.

Managed code, including applications, runtime, and driver, have a priori knowledge of the client's exact hardware configuration, just as the JIT compiler has a priori knowledge of the microprocessor type on the target computer system. At compile time, the compiler knows the effective version various system drivers, so that the compiler can emit an executable tuned for a particular driver version and target system.

The present invention relates to systems and methods that facilitate dynamic programming language execution in a managed code environment. A class component is provided that declares an inheritance hierarchy for one or more tagged values associated with a dynamic programming language. During execution of the tagged values, a rules component mitigates user-defined types from inheriting or deriving properties from the tagged values in order to support a type safe runtime environment. A bifurcated class tree is provided that defines non-tagged type elements on one side of the tree and tagged type element values on an alternate branch of the tree. The rules component analyzes runtime extensions that help to prevent data from one component of the tree deriving or inheriting properties from another component of the tree. The runtime extensions include such aspects as cast class extensions, test class extensions, and conversion class extensions for converting data types from one class subtype to another.

Unsafe application programs that implement managed code can be executed in a secure fashion. In particular, an operating system can be configured to execute an application program in user mode, but handle managed code compilation through a type-safe JIT compiler operating in kernel mode. The operating system can also designate a single memory location to be accessed through multiple address spaces with different permission sets. An application program operating in user mode can be executed in the read/execute address space, while the JIT compiler operates in a read/write address space. When encountering one or more pointers to intermediate language code, the application runtime can send one or more compilation requests to a kernel mode security component, which validates the requests. If validated, the JIT compiler will compile the requested intermediate language code, and the application program can access the compiled code from a shared memory heap.

A system and method is provided for efficiently pinning references to the managed heap. The system and method allow for references to managed objects to be declared as pinned during a call to unmanaged code. The references are then reported as pinned to a garbage collector in response to invocation of a garbage collection service. The reference can be declared as pinned by a programmer within the source code or automatically invoked at run-time based on an unsafe condition. The garbage collection service will not move or relocate objects that are referenced by the active pinned local variables. If a garbage collection does not occur, the fact that the local variables are declared pinned is ignored.

A processor comprising one or more control units, a plurality of first execution units, and one or more second execution units. Fetched instructions that conform to a processor instruction set are dispatched to the first execution units. Fetched instructions that conform to a second instruction set (different from the processor instruction set) are dispatched to the second execution units. The second execution units may be configured to performing graphics operations, or other specialized functions such as executing Java bytecode, managed code, video/audio processing operations, encryption/decryption operations etc. The second execution units may be configured to operate in a coprocessor-like fashion. A single control unit may handle the fetch, decode and scheduling for all the executions units. Alternatively, multiple control units may handle different subsets of the executions units.

A method and apparatus for providing instrumentation data to an instrumentation data source from within a managed code environment is provided. A decoupled provider is provided that executes partially in managed code and partially in unmanaged code. The decoupled provider facilitates communication with an instrumentation data source. The decoupled provider also dynamically registers schema for managed code objects to be instrumented at run-time. The decoupled provider also receives and processes requests from the instrumentation data source to retrieve instance data for managed code objects, to write properties on managed code objects, and to execute methods on managed code objects.

In the access control model of security, an access control matrix associates rights for operations on objects with subjects. An approach for assigning rights to code at run-time involves determining the run-time rights of a piece of code by examining the attributes of the pieces of code that have run (including their origins) and any explicit requests to augment rights. Thus, this approach relies on the execution history for security. This history based approach reduces the difficulties and the error-proneness of securing extensible software systems.

An instrumentation client API is provided within a managed code runtime environment for accessing instrumentation data that resides outside of the managed code runtime environment. The instrumentation client API provides access to instrumentation data in a manner that is consistent with the classes and models provided by the runtime environment, raises exceptions in a manner that is compatible with the runtime environment, and is secure. The instrumentation client API wraps, or translates, calls to and from an instrumentation data source external to the runtime environment. The API interacts with an interface provided by the instrumentation data source to provide functionality and connectivity that is not otherwise provided by the instrumentation data source. The API also provides access to instrumentation data in a manner that is consistent with the models and classes provided by the runtime platform. The classes defined by the API return collections and exceptions in a way that is consistent with the managed code runtime platform.

A system and method for facilitating cross-process access into a managed code process is useful in an embodiment of the invention for debugging managed code without perturbing the process being accessed or requiring the code under test to be running during debugging. A compiler according to an embodiment of the invention is used to produce mirror code wherein in-process pointers have been replaced with cross-process pointers in order to mirror the address space of the process under test to the address space of the mirror code process. In a further embodiment, the mirror code process is modified not only to allow but also to optimize the cross-process access.

A system and method for inducing asynchronous behavioral changes in a managed application process is presented. An application manager process is executed. A managed application process is executed. At least one application provided as object-oriented program code under the control of a managed code platform is executed. The managed application process logically communicates with the application manager process. One or more constructors corresponding to notifiable objects provided as object-oriented program code are identified. Each constructor keeps track of instantiated notifiable objects in a list in the managed application process. A change request is broadcast to the managed application process. The notifiable objects tracked by each identified constructor are iterated over to effect a behavioral change in the managed application process.

The present invention provides an object model that exposes speech-related functionality to applications that target a managed code environment. In one embodiment, the object model and associated interfaces are implemented consistently with other non-speech related interfaces supported across a platform.

A method of managing code-tracing data is described. The method comprises the steps of: receiving code-tracing data from an executing software component; adding the received code-tracing data to a log stored in temporary storage; detecting a property of the received code-tracing data; copying the log to non-volatile storage when the property matches a defined trigger property; and deleting contents of the log according to a caching policy when the property does not match a defined trigger property.

Described is a system and method that separates a managed code runtime library or program into four parts, comprising a header, resources, metadata and method implementations. The metadata and some or all of the resources are maintained in system memory (RAM) the entire time that the program is running. The method implementations and any non-maintained resources are loaded on demand, and then discarded such as via garbage collection. The amount of memory consumed by a managed code program is thus reduced relative to non-separated environments, but because the metadata and selected resources are in memory, the program execution is highly efficient due to significantly reduced access of data in non-volatile storage. The parts of the assembly that are maintained in RAM can be saved as code library files, providing shared use by programs and efficient loading by eliminating any need to again parse a program to identify the separate parts.

Documentation having code samples is managed. Documentation describing programming code for a software product is received. The documentation references a code sample having an associated test module for determining whether the code sample is valid. The code sample is tested by executing the associated test module to produce a test result indicating whether the code sample is valid. The documentation, code sample, and test result are stored. The documentation, code sample, and test result may be provided to a client adapted to display the code sample and test result to a user of the client. Invalid code samples in the documentation may be identified using the test modules and the invalid code samples may be replaced to make the code samples valid.

One embodiment of the present invention sets forth a method for enabling an intermediate code-based application program to access a target graphics processing unit (GPU) in a parallel processing environment. The method includes the steps of compiling a source code of the intermediate code-based application program to an intermediate code, translating the intermediate code to a PTX instruction code, and translating the PTX instruction code to a machine code executable by the target graphics processing unit before delivering the machine code to the target GPU.

Systems, apparatus, methods, and articles of manufacture provide for managing code deployment. In one example implementation, after packaging application code, a code deployment system defines a first container and a second container for a container-as-a-service (CaaS) service, based on the application code package. The example system then uses the CaaS service to automatically conduct a first container test of the first container, and, in parallel, to automatically conduct a second container test of the second container.

A computer readable medium stores a program for managing multiple types of middleware transport modules for accessing business logic. The computer readable medium includes a first starting code segment for starting a first middleware transport module of the multiple types of middleware transport modules as a main thread; a second starting code segment for starting a second middleware transport module as a slave thread; and a managing code segment for managing the main thread and the slave thread. The slave thread is managed in accordance with the managing of the main thread, and a functionality of the slave thread remains independent of a functionality of the main thread. Managing the slave thread may include shutting down the slave thread in response to shutting down the main thread.

Described is a mechanism for executing a hosted application in either a browser-execution environment or as a standalone application. The invention provides a mechanism that enables hosting code in either of plural hosting environments. Briefly stated, code is created that executes in a common execution environment. That execution environment can be either owned by a browser or not. When the code is launched, a host sniffer component determines from an indicator within the code which hosting environment is appropriate. Based on that indicator, the code is launched in the appropriate hosting environment. The appropriate hosting environment may be either browser hosted or standalone.