Provided are a computer program product, system, and method for generating a visualization of blocks of code statements related to errors in a log file. A log file logs errors in execution of program code. Source code, from which the program code is compiled, is analyzed to determine blocks of statements in the source code whose execution resulted in the errors in the log file. Blocks of statements in the source code are annotated with the errors in the log file caused by the blocks of statements. Execution of a block of statements annotated with an error resulted in the error logged in the log file. The annotated blocks of statements are processed to generate a video providing a visualization of the blocks of statements in the source code whose execution resulted in the errors.

Operations may include obtaining a plurality of posts from one or more web sites, each post including a respective buggy snippet of source code that includes a corresponding error. The operations may also include generating a plurality of bug patterns from the plurality of posts in which each respective bug pattern corresponds to a respective buggy snippet and indicates a corresponding bug scenario that leads to the corresponding error of the respective buggy snippet that corresponds to the respective bug pattern. The operations may also include determining similarities with respect to the respective bug patterns and selecting, based on the similarity determinations, a first bug pattern of the plurality of bug patterns for revision. In addition, the operations may include obtaining a revised bug pattern that is a revised version of the first bug pattern.

For the purpose of reproducing a call stack accurately without restricting the range of application, a stack scanner extracts, from a stack area of a thread whose call stack is to be acquired in a memory space of an application process, possible return addresses that are addresses in a feasible region in the memory space each representing a command right after a function call command. A program analyzer analyzes a control flow representing a flow of control configured by a branch in a function that is called by the function call command right before the command represented by each of the possible return addresses and, when there is a route reaching a command currently being executed in the control flow, determines that the possible return address is a return address and, when there is not the route, determines that the possible return address is not a return address.

A method for locating a fault information is provided. The method includes: parsing error information of a target application to obtain version information and an error attribute of the target application; determining, based on the version information, a target mapping file corresponding to the error information; and determining a target location by utilizing the error attribute and the target mapping file, where the target location is used to determine a location of fault description content.

Generating error event descriptions by receiving a set of error messages associated with an error event, generating a tokenization of at least one line of the set of error messages, providing the tokenization to an attention head according to a context of the tokenization, providing an output of the attention head as input to a generative model, generating a description of the error event according to the output, and providing the description to a user.

A system has a memory programmed with multiple firmware images each having an associated distinct entry point, a processor, a writable hardware register, and a controller external to the processor that, prior to each reset of a sequence of resets of the processor, reads the entry point of a firmware image from the hardware register and causes the processor to begin fetching instructions at the entry point read from the hardware register. The firmware images include boot, mission mode, and at least one other firmware image. The memory may be writeable with a modifiable version of a post-production mission mode, debug, prototype, or patched ROM firmware image. A second controller writes a second entry point to the hardware register prior to an initial reset such that the external controller reads the second entry point and causes fetching instructions at the second entry point rather than the initial entry point.

Examples described herein include systems and methods for fuzz testing low-level virtual devices and virtual devices with DMA write functionality. A fuzz tester includes components distributed across a virtual machine and its host system. The fuzz testing components in the virtual machine are implemented as firmware installed in the virtual machine's ROM. These components operate independent of data stored in the virtual machine's RAM and do not require an operating system to be installed on the virtual machine. As a result, any changes made to the virtual machine's RAM during the fuzzing process by low-level virtual devices or virtual devices with DMA write functionality cannot interrupt the fuzz testing or otherwise negatively impact the fuzz tester itself.

A debug support program causes a computer to execute a step of extracting a set of variables having a dependency relation from a plurality of variables written in a plurality of process blocks that are included in a sequence program and each describe a process per device, that is to say, a process per slave device; a step of collecting log information recording information regarding input of a value to each of the plurality of variables written in the process blocks; a step of correcting an extraction result regarding the dependency relation on the basis of contents of the collected log information; and a step of presenting a corrected extraction result.

Techniques are described herein that are capable of automatically generating, revising, and/or executing troubleshooting guide(s). In a first example, an operation is selected based at least in part on a schema and information indicating that the operation is capable of mitigating a category of issues. In a second example, information is analyzed to identify operations performed with regard to service(s) to mitigate issues, and an operation is selected based at least in part on the information indicating that the operation is capable of mitigating a category of issues that includes an identified issue. In these examples, an executable troubleshooting guide is automatically generated to perform the selected operation. In a third example, weights are assigned to features that are extracted from data associated with troubleshooting guide(s), and a subset of the troubleshooting guide(s) is automatically revised based at least in part on the weights corresponding to the subset.

Embodiments of the present disclosure provide a method, an electronic device, and a computer program product for code defect detection. The method described here includes determining log information associated with a defect based on the defect reported during testing of a software product. The method further includes determining a nature of the defect based on the log information. The method further includes determining, based on the nature, the log information, and a memory image file generated when the defect is reported, target code in code of the software product that causes the defect, in response to the nature indicating that the defect is caused by the code of the software product and needs to be repaired. By using the solution of the present application, different analysis strategies for defects may be adopted based on natures of the defects, thereby improving the efficiency of detecting code defects.