A computer device includes a memory. The computer device also includes at least one processor configured to execute a process and manage the memory for the process. The processor is further configured to execute one or more program instructions associated with an application, reach control flow transfer for the one or more program instructions, unwind a call stack associated with the one or more program instructions in response to a failure to meet a target control flow, identify an offending function call, and rewrite the offending function call. The rewritten function call includes a memory operation boundary check.

A computer-implemented system and method detect an error in an application comprising a component having a control that is displayed in a first state on a display device. Responsive to the detecting of the error, the method comprises associating the error with the control, and, upon making this association, the method comprises automatically modifying the component at application run-time. This modification indicates that the control is no longer functional. A display operation of the component is performed where the modified component has: a) the control displayed in a second state on the component, or b) the control is removed from the component. The method may be repeated when other errors occur, and the control may be restored when the underlying error is resolved.

Example implementations relate to automatic diagnostic mode to identify a potential cause of a boot problem of a system. In an example, the automatic diagnostic mode iteratively isolates subsystems of the system in coordination with a baseboard management controller. For each iteration of subsystem isolation, a system boot is executed while a subsystem is isolated. The system boot is monitored against a watchdog timer of the baseboard management controller to determine if the system boot is successful. If the system boot is successful, the isolated subsystem is marked as a potential cause of the boot problem of the system. If the system boot is unsuccessful, the automatic diagnostic mode continues to iteratively isolate the subsystems.

A computer-implemented runtime system is operable of providing a continuous product execution runtime environment for an application via a healthcare network. The system includes a focus machine and an action plan repository, to provide an autonomous runtime environment by at least: monitoring a running use case of at least one application on at least one device; taking over responsibility of a running use case of the at least one application, upon an error state being detected for the monitored running use case; analyzing the error state of the running use case detected; obtaining at least one suitable substitution action out of a plurality of actions deposited in the action plan repository, based on the error state of the running use case analyzed; and terminating and completing at least a part of the running use case, by employing the at least one substitution actions obtained, on the at least one application.

Apparatuses, methods and storage medium associated with embedded computing, are disclosed herein. In embodiments, an embedded computing platform includes a plurality of system-on-chips (SoCs) forming a local compute cluster; and an orchestrator disposed on one of the SoCs arranged to orchestrate fail-safe operations, in response to a reported unrecoverable failure requiring shut down or partial disabling of one of the SoCs, to consolidate execution of critical workloads on one or more of remaining fully or partially operational ones of the SoCs. Other embodiments are also described and claimed.

Disclosed are systems, methods, and articles for determining compatibility of a mobile application and operating system on a mobile device. In some aspects, a method includes receiving one or more data values from a mobile device having a mobile medical software application installed thereon, the data value(s) characterizing a version of the software application, a version of an operating system installed on the mobile device, and one or more attributes of the mobile device; determining whether the mobile medical software application is compatible with the operating system by at least comparing the received data value(s) to one or more test values in a configuration file; and sending a message to the mobile device based on the determining, the message causing the software application to operate in one or more of a normal mode, a safe mode, and a non-operational mode.

Example implementations relate to automatic diagnostic mode to identify a potential cause of a boot problem of a system. In an example, the automatic diagnostic mode iteratively isolates subsystems of the system in coordination with a baseboard management controller. For each iteration of subsystem isolation, a system boot is executed while a subsystem is isolated. The system boot is monitored against a watchdog timer of the baseboard management controller to determine if the system boot is successful. If the system boot is successful, the isolated subsystem is marked as a potential cause of the boot problem of the system. If the system boot is unsuccessful, the automatic diagnostic mode continues to iteratively isolate the subsystems.

A method is provided. The method of resetting a system, comprising: receiving data from the electronic sub-system; determine if a non-hardware fault is detected; if a non-hardware fault is detected, then performing a software reset of the electronics sub-system; if no non-hardware fault has been detected, then determining if a hardware fault is detected; and if a hardware fault is detected, then performing a hardware reset of the system.

Approaches for managing applications in a cluster are described. In an example, a first agent may be executing on a first programmable network adapter card installed within a first computing node within a cluster. The first agent may isolate an application executing on the first computing node. Thereafter, the application may be managed by the second computing node.

In a shared backup ECU, a diagnostic section diagnoses an abnormality in a plurality of ECUs which, in order to perform an individual function, execute a program that is different according to the function. A loading section loads, from a storage section storing a plurality of programs in advance, a program which is the same as a program to be executed by an abnormal unit being an ECU whose abnormality has been detected by the diagnostic section. An execution section executes the program loaded by the loading section, thereby performing a function which is the same as a function of the abnormal unit on behalf of the abnormal unit.