231 results about "Software bug" patented technology

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 system and a method of rating software bugs using a bug scoring and tracking system is presented. The system and method may use automated scoring of the bugs to determine the impact of the bug. The system and method may connect to one or more databases to determine the extent of the deployment of the software, the impact of the bug, and/or the history of the bug. Scoring is used to prioritize the bugs and the scoring is extensible and adjustable allowing easy addition of new parameters and allowing the system to be modified for different bug types, software, or customers.

A system for application reference testing (SMART) solves the technical problem of generating test data and test cases from graphical user interface applications (GAPs) to test web services, effectively and non-invasively. SMART allows organizations to easily and promptly identify and resolve software bugs, ensure higher quality software and development productivity, complete software projects faster, deliver software products to market quicker, and improve the return on investment for software development projects. SMART provides a user friendly visualization mechanism that interacts with an accessibility layer to enable organizations to economically and easily define user interactions with GAPs, by performing point-and-click, drag-and-drop operations on the GAPs, and generate reusable test data and test cases for web services.

The embodiment of the invention provides a method and a device for updating terminal patches on line. The method comprises the following steps of: establishing a patch database on a terminal side; acquiring an updated patch file list from a server, wherein the patch file list comprises an identifier of each patch and a storage route thereof; downloading patch files according to the updated patch file list and storing the patch files into a local temporary directory; adding the downloaded patch files and the storage routes thereof into the patch database; and covering the original files in thestorage routes corresponding to the patch files by the patch files in the temporary directory. In the technical scheme of the embodiment, the terminal can update a software bug on line and a user does not need to update the whole system version of the terminal again; and at the same time, private data of the user is not lost during the repair of the software bug.

Provided is a process of estimating time to address software-issue reports describing software bugs or feature requests in software project management computer systems based on historical performance in addressing previous software-issue reports, the process including: obtaining the workflow instance records; constructing a time-estimation model based on correlation between features of the workflow instance records and durations of time before or during execution of some or all of respective workflow instances; obtaining a workflow instance that is not completed; estimating a duration of time for the task with the time-estimation model.

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.

The invention relates to a system for detecting a software bug triggered during practical running of a computer program in the technical field of computers. The system comprises a binary code dynamic inserting module, a program basic block recognizing module, a function call graph constructing module, a control flow graph constructing module, a function recognizing module and a static analysis module. By combining two technologies of dynamic program analysis and static analysis path complementation, the invention not only can detect the bugs which can be triggered during the practical running of the program but also can reach higher program path coverage rate, carry out bug detects on the path which is not covered in the dynamic analysis process, improve the success rate of bug detection and reduce the false rate of the bugs. Meanwhile, the static analysis path complementation technology only analyzes a path which is not executed in dynamic analysis instead of all program paths, thereby greatly reducing the cost on time and system resources.

The invention provides a method and device for detecting integrated or customized open source project bugs in software and relates to the technical field of software bug detecting. The method includes the steps that original bug information of an open source project is obtained from a preset gather library; according to the original bug information of the open source project, bug description information, bug influenced software or component version information and bug detection detail feature information of the open source project are extracted; according to the bug description information, bug influenced software or component version information and bug detection detail feature information of the open source project, a bug detection database is established; the bug detection database comprises all detection items which are arrayed according to a preset index sequence; a code and an executable file of software to be detected are extracted from the software to be detected; according to all the detection items in the bug detection database, the code and the executable file of the software to be detected are sequentially matched and detected according to the preset index sequence so as to determine whether the bugs exist in the integrated or customized open source project in the software to be detected or not.

In one embodiment, a method for automatically identifying a program error in a computer program includes receiving a program error message indicating that a new program error has occurred during execution of the program and generating a program stack trace for the new program error indicating the source of the new program error within the program. A first operation is applied to a portion of the program stack trace to generate a first numerical code associated with the new program error. The first numerical code associated with the new program error is compared to one or more stored first numerical codes associated with previously identified program errors to determine whether the new program error is the same as a previously identified program error. If so, stored information associated with resolving the previously identified program error is provided for use in resolving the new program error.

A probabilistic machine learning model is generated to identify potential bugs in a source code file. Source code files with and without bugs are analyzed to find features indicative of a pattern of the context of a software bug, wherein the context is based on a syntactic structure of the source code. The features may be extracted from a line of source code, a method, a class and/or any combination thereof. The features are then converted into a binary representation of feature vectors that train a machine learning model to predict the likelihood of a software bug in a source code file.

The invention discloses a method used for reporting the program crash information, which aims at solving the problems of hard statistics and analysis of the program mistakes and inconvenient optimizing of the program in the prior art caused by the non-reporting of the program crash information. The method captures the error address and error message when the program is crashed, taking advantage of the detecting program and reports to the server via the reporting program, while the server analyzes the error address and error message reported when the application program is crashed, and classifies and stores the error message according to the error address. At the same time, the invention discloses a processing system for program crash information.

A system for determining driver errors includes an interface and a processor. The interface is configured to receive a safety warning from a safety warning system. The processor is configured to determine an appropriate driver response based at least in part on the safety warning; determine a driver response; determine whether the driver response comprises the appropriate driver response; and in the event the driver response does not comprise the appropriate driver response, indicating a driver error.

The invention discloses a method for checking consistency of a schematic diagram and PCB production data. The method comprises steps as follows: making a standard template of a PCB design software schematic diagram netlist file; making a standard template of an ODB++processing data netlist file; extracting a PCB design software schematic diagram netlist, and extracting a processing data netlist; analyzing the netlists, and storing connecting relation description information, device type information, abidance device information, connection node number, connection nodes and a terminator protocol in a list manner; comparing theschematic diagram netlist file with the processing data netlist file according to a defined data storage protocol; generating a report file according to a comparison result. According to the method, the problems of network loss, short circuit and the like caused by negligence, software bug and the like in a PCB design process are solved, time cost consumed by a designer for connecting relation correction is saved, and the method is better than a currently utilized IPC (inter-process communication) netlist comparison method in the aspects of accuracy and efficiency.

The invention discloses a firmware upgrading system based on communication interfaces and belongs to the technical field of electrons. A circuit structure comprises a communication interface module, a main controller module, a memory medium module and a mandatory upgrading module, wherein the main controller module comprises a main controller chip and a program firmware module. A user can obtain the latest firmware conveniently in real time, upgrade the system, timely eliminate various software bugs and acquire the latest functions during device operation, rights and interests of the user are guaranteed, simultaneously, operation in the upgrading process is convenient, and time of the user and a manufacture is not delayed due to upgrading of the firmware, so that the cost is saved. The program firmware module is composed of a guide module, an operation module and a backup module, can conduct upgrading and restoration of the firmware and provides a manual mandatory upgrading function, so that the real zero-risk upgrading is achieved.

A system and method for updating a software acceptance testing database via a communications network is disclosed. A database maintained at a server is accessed by remote users via a restricted communications network. Mobile personnel log trouble tickets, the software vendor assigns the trouble ticket to a resolution entity, the software purchaser is notified when the problem is to be fixed, the problem is retested and the results of the retest are logged. For future releases of the software, a field is included in the database for trouble items that will be included in future regression testing procedures.

A digital computer call stack or combined call stack and data stack is traced and analyzed following the occurrence of an unhandled exception or crash. Stack frame sizes and other artifacts are used to form a distinctive stack signature that generally reflects execution of the program up to the point of failure, without being finely detailed. Stack signatures can be associated with program bugs, and stack signatures collected from other failure instances, at other times or on other machines, can be conveniently compared for recognizing particular types of failures, without access to source code and without detailed study of memory dumps.

A system method and computer-readable media for searching an object oriented database are provided. The present invention may be employed to detect software bugs, deficiencies and/or errors in, affecting, or related to, an object database management system. The invented technique may use an SQL table join query to search for incomplete, damaged or erroneous software objects.

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.