Hewlett Packard Enterprise Development LP

Hewlett-packard Development Company, L.p.

Rajesh Kumar Chaurasia

Abhay Padlia

Arijit Chatterjee

Sujoy Saraswati

Suprateeka Radhakrishna Hegde

Padmagandha Panigrahy

Padmanabhan Selvakumarapalayam Nagarajan

Deepti Kharbanda

Deepak Sreedhar

Anand Satish Phatak

Some examples relate to performing application-defined object logging through a file system journal. In an example, a file system may determine during execution of an operation for an application whether a callback function is specified for the operation. In response to the determination, file system may invoke the callback function. File system may receive an object defined by the application. File system may link a copy of the object with a file system transaction associated with the operation in a journal of file system. File system may determine whether file system transaction is committed. In response to the determination, file system may write a copy of the object from the journal to an event log file. File system may allow the application to determine whether file system transaction is committed by enabling access to the event log file.

Application-defined object logging through a file system journal

Some examples described herein relate to dynamically applying a patch to a shared library. An external process may be invoked to bring target processes that refer to a shared library, to a safe point. In response to a function call from a target process, amongst the target processes, to access a target function in the shared library, the function call may be forwarded to a special function in a dynamic loader, wherein the target function is a function to be patched in the shared library. The special function may determine whether a shared patch library, comprising a patched version of the target function or a new function, is loaded for the target process. In response to determination that the shared patch library is not loaded for the target process, the shared patch library may be loaded only for the target process, and the request for the target function may be routed to the patched version of the target function or the new function, in the shared patch library.

Dynamically applying a patch to a shared library

Provided is a method of preserving object code translations of a library for future reuse by an emulator. A munmap() system call is intercepted from an application for unmapping a mapped library memory address. A determination is made if an entry related to the mapped library memory address is present in a first predefined data structure. If said entry is present, a determination is made if the mapped library memory address corresponds to a library text or library data. If the mapped memory address corresponds to the library text, said entry is flagged as inactive in the first predefined data structure, and an object code translation of the library text is preserved in the mapped library memory address. If the mapped library memory address corresponds to the library data, contents of the mapped address are reset to zero.

Preserving object code translations of a library for future reuse by an emulator

The method, an apparatus, and/or a system of cross-platform architecture for replicating profiling scheme in a computer system are disclosed. In one embodiment, a method for forming profiling information of one computer platform in another computer platform includes generating instrumented code by a code instrumenter using a target platform code. The method further includes generating the profile information that the source platform profiling tools can decipher and utilize using the instrumented code, and generating a profile report by analyzing the generated profile information using the source platform profiling tools in a dynamic binary translator that can be used by the dynamic binary translator (DBT) to generate target platform code. In addition, the method may include translating source platform object code into the target platform code using the DBT.

Cross-platform architecture for replicating profiling scheme in a computer system

A core file derived from an application crash is created. The application belongs to a source platform and is run on a target platform. The application is emulated on the target platform. In response to the crash occurring, detecting whether the crash corresponds to the failure of a process corresponding to the emulated application. The crash process is mediated by intercepting information relating to the failure of the emulated application and writing a core file corresponding to the failure of the emulated application running on the source platform. A dynamic binary translator performs the steps and debugs an emulated application as if it had crashed and dumped a core file on its native platform.

Growing community of inventors

Bengaluru, India

Rajesh Kumar Chaurasia