190 results about "Software error" patented technology

In accordance with the present invention, there is provided a client application for enabling access to an online service and displaying advertisements while the user is accessing the online service. The client application receives play lists from the online service provider. The play lists include information about advertisements to be played and the order of play. In conjunction with the client application displaying advertisements, the client application and an online service provider server also track and record the occurrence of hardware and software errors and malfunctions that occur in relation to the provision of the online service. The types of errors may include errors in a communication channel from a local device to an online service provider server, data access errors, and any other errors that may occur in the operation of software and hardware, such as software crashes and the incorrect display of advertisements.

The invention describes an automated software support system comprising automated bug filing and test case creation component to checkpoint a client process initial state and record the client process initial state changes while the client process undergoes sequence of states which need to be analyzed, such as software bug, deliver the recordings to a development node, where the problem can be debugged without reproducing the client process environment by using the recorded state to recreate initial state of the client program and by using the recorded log to simulate the client program execution forwards and backwards.

Multiple versions of a runtime system, such as a software emulation application that emulates a legacy hardware architecture, are allowed to co-exist in the memory of a new hardware architecture. The operating system software of the new hardware architecture reads configuration data from a database or table to decide which version of the runtime system is desirable for an application program or game that is being loaded or is currently running, and, if a match is found, only that runtime system is invoked. To reduce storage footprint, the different versions of the runtime system may be stored using “differential patching” techniques. In this configuration, the operating system will always launch the same basic runtime system binary, but it will select a different differential patch to apply at run-time based on the title as determined during the database lookup. In this fashion, future changes to the runtime system to correct software bugs, incompatibility issues, and the like only need to be tested for the relevant target application programs or games.

A device and method supporting the identification and correction of firmware and / or software errors is described. Upon the occurrence of a firmware / software error or exception, an embodiment in accordance with the present invention may gather parameters for identifying the error or exception, and the execution environment in which the error occurred, and may communicate the parameters or an identifier to a server, to retrieve update information for correcting the firmware / software error or exception. The execution environment may be single or multi-threaded, and may be a java virtual machine. The device may restart / reboot during the update process, and may log an error if update information is not available to correct the error or exception. The device may communicate the error log information to the server via the communication network. The communication network may be a wireless network.

In accordance with the present invention, there is provided a client application for enabling access to an online service and displaying advertisements while the user is accessing the online service. The client application receives play lists from the online service provider. The play lists include information about advertisements to be played and the order of play. In conjunction with the client application displaying advertisements, the client application and an online service provider server also track and record the occurrence of hardware and software errors and malfunctions that occur in relation to the provision of the online service. The types of errors may include errors in a communication channel from a local device to an online service provider server, data access errors, and any other errors that may occur in the operation of software and hardware, such as software crashes and the incorrect display of advertisements.

A system and method is provided to improve software simulation. A software emulator is used in conjunction with a hardware simulator. A special snapshot instruction is included in the software code that is emulated. When the snapshot instruction is encountered, values such as register, memory, and program stack values, are stored creating an initial snapshot. Code continues to be emulated and, when the next snapshot instruction is encountered, the values are written to create a second snapshot. The initial values are used to set an initial state in a hardware model that is simulated on a hardware simulator. The results of the hardware simulation are compared to the second snapshot to uncover software errors and / or hardware errors so that the software can be modified or the hardware design can be modified. Multiple sets of snapshots can be taken to analyze multiple sections of the software program.

The invention provides a method and system for automatically reproducing and positioning a software error. The method comprises the steps of: recording an input operation of a user and an operated object, defining and generating a log document; when software has an error, analyzing the log document, and reducing the input operation of the user and the operated object; and simulating the input operation of the user according to the reduced input operation of the user and the reduced operated object, reproducing the error and automatically reproducing and positioning the error and rapidly finding a design defect of the software.

Error reporting software-based method where an error list for a currently-running version of some target software (or firmware) is compared to an error list for a previous versions. Helpful information can be gleaned from the comparison of error lists. For example, if it is known that the hardware configuration has not changed, as between the two lists, and there is an error on the current list that does not appear on the previous list, then this indicates that the error is in the software update and is not a hardware problem.

The risk of inadvertent introduction of software bugs to a large number of users during a software update is minimized by controlling updates using a uniform mechanism of sending updates to seed users. A value-generating module generates a value for a computer, the value falling within a population range of values. A sampling range-generating module generates a sampling range of values as a proper subset of the population range, the probability of the random value falling within the sampling range being predetermined. An eligibility determination module determines whether the computer is eligible to receive a software update, the computer being determined eligible when the random value for the computer falls within the sampling range, and an update module provides the software update to the computer based on the eligibility determination. In some embodiments, a problem review module determines whether the update has caused a problem for computers receiving the update.

A method or apparatus determines an order for installing software patches by comparing information in the software patches. The information may include files created or modified to fix software errors in a software program and metadata referring to the files. By comparing the information, the method or apparatus may determine whether at least two of the software patches include files in common. Based on the results of comparing the information, the method or apparatus may automatically determine an order for installing the software patches into the software program. The files in a given software patch may be used to fix unrelated software errors. The metadata may refer to a time at which the files in the software patches were created or modified, and the order of installation may occur in a chronological manner based on creation or modification dates.

Provided are techniques for receiving an error inject script that describes one or more error inject scenarios that define under which conditions at least one error inject is to be executed and compiling the error inject script to output an error inject data structure. While executing code that includes the error inject, an indication that an event has been triggered is received, conditions defined in the one or more error inject scenarios are evaluated using the error inject data structure, and, for each of the conditions that evaluates to true, one or more actions defined in the error inject script for the condition are performed.

A battery management system (BMS) in which a battery protection circuit controls a main switch using hardware without software control, thereby coping with troubles in the BMS or software errors.

Systems and methods consistent with the invention may include receiving an indication that a software error was detected during operation of the application program, generating an error message based on the software error, the error message including an error signature, comparing the error signature with information stored in a patch library database to identify a corresponding correction patch, and correcting, when the corresponding correction patch is identified, the software error by applying the corresponding correction patch.

A system for self-diagnosing and error reporting of a software application in a computer system having a plurality of software applications and background processes, the system comprising a diagnosis module configured to collect and monitor usage data of resources of the computer system, execution status of the software applications and background processes of the computer system, and software application error conditions, adjust logging level of log files according to the execution status of the software applications and background processes of the computer system and the software application error conditions, and generate diagnosis advisory based on the usage data of the resources of the computer system and the software error conditions, and a reporting module configured to collect and report the usage data of the resources of the computer system, the log files and the generated diagnosis advisory automatically to a user.

The invention discloses a coordination control method for a micro-grid system. The coordination control method of the micro-grid system comprises the steps of: (1) performing program initialization of a coordination control system; (2) processing a digital switching value, and carrying out information interaction with a micro-grid energy management system, a liquid crystal display module and an in-place controller; (3) processing data of obtained information; (4) judging the working condition of the micro-grid, and calling a corresponding control program module based on the type of the working condition of the micro-grid; and (5) calculating the power command value of each running device, sending a signal to each running device of the micro-grid after the safety economic index satisfying with each running device is confirmed and adjusting the running state of the system by the control program module. The coordination control method for the micro-grid system realizes coordination control on the micro-grid system, and ensures safe and steady operation of the micro-grid. By adopting the modular software design and shortening the code of each software module, the coordination control method for the micro-grid system can remove software errors to the maximum extent and therefore greatly improve reliability of the software.

Method and system for facilitating analysis of causes of abnormalities found during a test on a video system. Video output from the system during the test, operation log of a test worker, and images generated by image analysis unit analyzing characteristic quantities of the video output from the system and determining points of change of the video and moving objects in the video, are recorded in storage device. Relation between the direction of the moving objects in the video and the direction of user input operations is checked and the moving objects in the video are classified into user-manipulation objects and non-manipulation objects and recorded. Abnormality occurrence locations are recorded. Recorded data are searched, classified and displayed by using as a key the abnormality categories, operation patterns of the operation logs, images of abnormality occurrence scenes and images of manipulation objects.

In a cause categorization step, bugs are categorized according to technical causes. In a damage evaluation step, how many steps the process has turned back due to a bug is measured. In a damage calculation step, damages are calculated for each bug technical cause. In a problem extraction step, a technical cause of which the damage is large is chosen as a problem. Then, in the bug database search step, a search for a measure for the bug technical cause extracted as a problem is performed with reference with a bug database so as to indicate an appropriate measure for a project.

An apparatus and method for detecting software error are provided. Trace files are respectively generated by a target machine and a functional simulator that imitates the target machine and performs the same operation as the target machine. Each of the trace files may include at least one of a data-flow-type trace including execution information about one or more instructions and a control-flow-type trace representing information about a part in which a change in address indicating the position of an instruction is a predetermined threshold value or more when the instruction is executed. By comparing the generated trace files, software error may be detected.

An apparatus for debugging source code includes a source code debugger configured to display state information and one or more initialization routines corresponding to a particular software function. The initialization routines initialize a target environment to a particular system state and facilitate replication, isolation, and analysis of software coding errors. In one embodiment, a function selector facilitates selection of the target function by a user and generates an execution request. In turn, a task dispatcher dispatches the initialization routines and associated software function in response to the execution request. The present invention greatly simplifies interactive debugging of source code. Rather than generating complex, error-prone, and often timing-dependent manipulation sequences of registers, memory, peripheral devices, and the like, a user simply selects the initialization routines that generate the particular states and conditions necessary to replicate and analyze a particular software error.

A system automatically detects and reports a hardware and / or software error in an X-ray system. A system automatically detects and identifies failed components of a distributed X-ray imaging system. Multiple different subsystems of an X-ray imaging system individually include, an executable procedure for detecting a failed component in a respective subsystem and a communication interface for initiating generation and communication of a message identifying the failed component and identifying the respective subsystem including the failed component. A repository stores data identifying failed components within the multiple different subsystems in response to the communicated message. An error processor accesses the repository of data and provides composite information enabling a user to identify failed components within an X-ray imaging system.

The present invention provides systems and methods for providing run-time type checking to prevent software errors. In architecture, a representative system includes a compiler that parses a program and further comprises a logic that generates a checksum for a block of code in the program, a logic that stores the checksum in the block of code, and a logic that inserts checksum instruction code into the block of code. The present invention can also be viewed as a method for providing run-time type checking to prevent software errors. A representative method operates by generating a checksum for a block of code in the program, and storing the checksum in the block of code. During execution of the program, a run-time checksum is generated for the block of code, and the block of code is executed if the checksum equals the run-time checksum, and the execution of the block of code is skipped if the checksum does not equals the run-time checksum.

A static random access memory has first and second complementary field-effect transistors. The first complementary field-effect transistor includes a semiconductor substrate, a first field-effect transistor of electron conduction type which has a first drain region constituting a Schottky junction and a gate electrode, and a first field-effect transistor of positive hole conduction type which shares the first drain region and has a shared gate electrode. The second complementary field-effect transistor includes a second field-effect transistor of electron conduction type which has a second drain region and a gate electrode, a second field-effect transistor of positive hole conduction type which shares the second drain region and has a shared gate electrode. The gate electrode shared by the first and second complementary field-effect transistors is connected to the common drain region of the mutually opposing complementary field-effect transistors, and the static random access memory has superior resistance to software errors.

A patch tool receives multiple patches, with each patch designed to fix a corresponding subset of a set of errors in a system. Some of the patches may require that the files from older patches be removed from the system. In an embodiment of the present invention, a developer of a patch is provided the flexibility to specify that a desired file from an older patch fixing a specific error, not be removed during deployment of a new patch designed to fix the same specific error. Rolling back later to the older version of the patch may be simplified by not removing the desired file.

Described is a system which includes an error handler to generate an error record in response to a software error in an embedded device and a non-volatile memory including a persistent memory region configured to store an error log, the error log configured to receive the error record, wherein the error log remains intact in the non-volatile memory after a reboot of the embedded device.

The invention relates to a wireless sensor network technology, and discloses an abnormal data analysis method and a wireless sensor node. The abnormal data analysis method comprises the following steps: S1, after a reading xt is obtained at a moment t by a node i, and whether the xt is an abnormal value or not is judged according to all readings in the current window, if yes, a step S2 is executed, and if no, a step S3 is executed; S2, readings of k neighbor nodes are obtained at the moment t by the node i, and the cause of the abnormal value of the xt is judged accordingly, if the cause is resulted from hardware or software errors, a step S4 is executed, otherwise, a step S5 is executed; S3, the xt is stored by the node I; S4, the xt is divorced from the node i; and S5, the xt is sent to a base station by the node i. The node comprises a data acquisition module, an abnormal data analysis module, a storage module and a wireless communication module. According to the technical scheme, the computation is finished within the neighbourhood of the node, so that the network flow expense is reduced; and by the use of the space-time relevance of data, the abnormal value is detected automatically, the cause of the abnormal value is analyzed, and the misdeclaration and false declaration events are avoided.

A remote management system includes a plurality of image processing devices which each detect their own first state information according to a power state transition or an operation, provide the first state information via a network, and respond to polling; and a management server which manages the first state information provided by each image processing device and second state information obtained from a response to polling, and manages a history of each image processing device based on the first state information and the second state information. The remote management system can remotely collect and manage operation state, error information that can cause a malfunction, error information generated by abnormal operation as well as malfunction of individual image processing devices and can collect / manage state information such as image processing device internal operation state information, image processing device malfunction, network connection failure, and software error.