Abstract: Displaying instrument output is disclosed. Instrument output data is received. A difference between two or more corresponding portions of data included in the received instrument output data is determined. At least a selected part of the received instrument output data is displayed in a manner that highlights the difference.

Abstract: Improving static analysis precision by recording a value pointed to by a string variable within the computer-based software application during the execution of a computer-based software application, modeling an invariant based on the recorded value, where the invariant represents at least one possible value pointed to by the string variable, performing a first static analysis of the computer-based software application to determine whether the invariant is valid with respect to the computer-based software application, and seeding a second static analysis of the computer-based software application with the invariant if the invariant is valid with respect to the computer-based software application.

Abstract: A method for visualizing execution of a program includes the steps of representing the program graphically as a flow diagram, and applying a marking to elements of the flow diagram as a function of state data of a state of the program that is being executed or has been executed.

Abstract: An approach to providing multiple concurrently executing debugging sessions for a currently executing operating system. The approach involves providing one first debugging session for debugging the currently executing operating system. The first debugging session has read access and write access to the data of the currently executing operating system. The approach also involves providing one or more second debugging sessions for the currently executing operating system. Each of the second debugging sessions has read-only access to the data of the currently executing operating system. The second debugging sessions run simultaneously with the first debugging session if the second debugging sessions are started while the first debugging session is active. As a result, multiple users can simultaneously debug the currently executing operating system. A lock may be used to ensure that only the first debugging session has write access to the data.

Abstract: A method, system and computer program product for generating appropriately sized core files used in diagnosing application crashes. An instruction pointer corresponding to the instruction that led to the application crash is identified. Address ranges of the garbage collection module and the compiler module are obtained. A determination is made as to whether the address of the instruction pointer lies within any of these address ranges for each stack frame in a crash stack. If it does not, then read or write instructions executed prior to the instruction that led to the application crash are identified for each stack frame in the crash stack. If a value of a register involved in such read or write instructions is within the address range of the compiled code buffers and/or heap, then the compiled code buffers and/or heap need to be included in the core file; otherwise, they do not.

Abstract: A programmable operating time period of at least one software unit is changed to a settable operating time period. Furthermore, a testing system for validating the system for setting the at least one settable operating time period is provided. Furthermore, the system is tested using the testing system, wherein the testing includes varying the at least one settable operating time period for detecting synchronization errors of the system. Thus, a test of a system including software units for synchronization errors is enabled by the targeted change of operating time period.

Abstract: A technique for debugging of a signal processing program or model (or the debugging and reconciliation of two independent software instantiations). Timelines (Vectors) of signal values for verification are condensed to a small amount of information, easy to understand and manage. The information is stored in “Intelligent Points”, which can be graphically specified by the test engineering. The Intelligent Points can include one or more attributes that describe how to generate the appropriate signals. The information so stored can then be automatically expanded to complete timelines.

Abstract: Systems and methods for identifying expressions that are potential causes of program bugs are disclosed. A program and at least one input resulting in at least one passing test of the program can be received. Further, at least one plausible repair candidate expression in the program can be identified. In addition, the methods and systems can determine whether replacement of the at least one identified expression with at least one value, which is different from a value provided by the at least one identified expression, maintains the passage of the at least one passing test. Moreover, the at least one identified expression can be output when the replacement maintains the passage of the at least one passing test to enable a determination of a modification of the program that repairs a bug in the program.

Abstract: Systems and methods are described for diagnosing behavior of software components in an application server. The application server can comprise a plurality of components that process incoming requests. A diagnostics advisor can be deployed with the application server and can determine an efficiency and/or inefficiency of each of the components of the application server or other middleware system. The efficiency determined by computing a ratio of a number of requests that completed execution in the component during a particular sampling time period to the number of requests that were received by the component during the sampling time period. The inefficiency is the inverse of efficiency, i.e. it is a ratio of the number of requests that are still being executed by the one or more components at the end of the sampling time period to the number of requests that were received by the one or more components during the sampling time period.

Abstract: A computer implemented method for dynamic test generation for concurrent programs, which uses a combination of concrete and symbolic execution of the program to systematically cover all the intra-thread program branches and inter-thread interleavings of shared accesses. In addition, a coverage summary based pruning technique, which is a general framework for soundly removing both redundant paths and redundant interleavings and is capable of speeding up dynamic testing exponentially. This pruning framework also allows flexible trade-offs between pruning power and computational overhead to be exploited using various approximations.

Abstract: A hashing tool can be used to generate Object UIDs from a software application. The software application can be tested. A change and release management system can receive Object UIDs involved in a defect uncovered during the testing. The change and release management system can receive names of functions involved in the defect uncovered during the testing and defect fixing. A graphical representation of function names versus Object UIDs for which the defect occurred can be created.

Abstract: Disclosed is a method for testing an application in a testing agent which resides on an application layer of a mobile communication terminal mounted with a platform designed so that applications of the application layer operate independently from each other and a command is not directly transferred between the applications. The method includes: receiving a command for testing a test target application from a testing apparatus; generating an event corresponding to the transferred command; and registering the generated event in a window manager positioned on a framework layer in order to transfer the generated event to the test target application.

Abstract: A method is provided for implementing multiple watchpoints or a watchpoint that is greater than one word in length. The method comprises a debugger receiving a watchpoint from a user, wherein the watchpoint identifies a portion of memory to be watched. The debugger then sends a read trap or write trap flag, for example READ_TRAP or WRITE_TRAP, to a memory protection module of an operating system identifying the portion of memory to be watched. A read or write operation is allowed on the watched portion of memory, but, after completion of the read or write operation, an exception signal is sent that indicates that the read or write operation occurred on the watched portion of memory. The debugger then provides output to a user regarding the exception.

Abstract: A computer implemented testing framework for symbolic trace analysis of observed concurrent traces that uses MAT-based reduction to obtain succinct encoding of concurrency constraints, resulting in quadratic formulation in terms of number of transitions. We also present encoding of various violation conditions. Especially, for data races and deadlocks, we present techniques to infer and encode the respective conditions. Our experimental results show the efficacy of such encoding compared to previous encoding using cubic formulation. We provided proof of correctness of our symbolic encoding.

Abstract: Disclosed is a novel computer implemented system, on demand service, computer program product and a method for fault-localization techniques that apply statistical analyses to execution data gathered from multiple tests. The present invention determines the fault-localization effectiveness of test suites generated according to several test-generation techniques based on combined concrete and symbolic (concolic) execution. These techniques are evaluated by applying the Ochiai fault-localization technique to generated test suites in order to localize 35 faults in four PHPWeb applications. The results show that the test-generation techniques under consideration produce test suites with similar high fault-localization effectiveness, when given a large time budget.

Abstract: A computer-implemented method for identifying a new software application to be developed. A computer database is searched for matching keywords that correspond to any of a group of selected keywords, indicative of the new application. The database contains descriptive keywords which are indicative of a set of existing applications. If no matching keywords are found in the database, then a description of the new application is requested from the potential user; the description of the new application is received from the potential user; and the description of the new application is used as a basis for developing the new application.

Abstract: In one embodiment, a method for testing adjustment and configuration is disclosed. The method can include accessing source code of a test framework that is configured for testing a module, creating a configuration folder having a property override for a test suite for the module testing, determining a source root folder for the test suite, starting the test framework by passing in an identifier for the test suite, and adding a custom test to the source root folder using the configuration folder to customize the test suite. The method can further include compiling the test framework with each of the plurality of test folders enabled. The method also may use a refactoring tool to make changes in a file within the test framework.

Abstract: In one embodiment, a processor includes an execution unit and at least one last branch record (LBR) register to store address information of a branch taken during program execution. This register may further store a transaction indicator to indicate whether the branch was taken during a transactional memory (TM) transaction. This register may further store an abort indicator to indicate whether the branch was caused by a transaction abort. Other embodiments are described and claimed.

Abstract: An attribute collector may collect an attribute set for each test entity of a plurality of test entities associated with a software test executed in a software environment. An attribute analysis signal handler may receive an attribute analysis signal associated with a change in the software environment, and a view generator may provide an attribute-based view associated with an affected attribute set associated with the change, the attribute-based view identifying an affected test entity that is affected by the change.

Abstract: A system and method for identifying bugs in a database system. In one embodiment, a method includes running a plurality of tests on a software application, and rerunning one or more tests of the plurality of tests. The method also includes identifying one or more bugs in the one or more tests based on inconsistent test results.

Abstract: A system and method provide for capturing architecture data for software executing on a system, wherein the architecture data can include state data and event data. The captured architecture data may be replayed in a simulator, wherein failure information corresponding to the software is obtained from the simulator.

Abstract: A non-intrusive debugging framework for parallel software based on a super multi-core framework is composed of a plurality of core clusters. Each of the core clusters includes a plurality of core processors and a debug node. Each of the core processors includes a DCP. The DCPs and the debug node are interconnected via at least one channel to constitute a communication network inside each of the core clusters. The core clusters are interconnected via a ring network. In this way, the memory inside each of the debug nodes constitutes a non-uniform debug memory space for debugging without affecting execution of the parallel program, such that it is applicable to current diversified dynamic debugging methods under the super multi-core system.

Abstract: Provided is a method for mitigating the effects of an application which crashes as the result of supplemental code (e.g., plug-in), particularly a plug-in from a source other than the source of the operating system of the device or the source of the application that crashes. The method includes executing the application. As the application is running, it may be monitored to determine if normal execution of instructions ceases. When that occurs, the system will make a determination if code from a supplemental code module was the cause of the crash, and will make an evaluation if that supplemental code module is from a source other than the source(s) of the operating system and application in question. In some implementations, remedial steps may be provided, such as providing information on subsequent executions of the application.

Abstract: In an aspect, the present application relates to a computer-implemented method, computer system, and computer program product for (automatically) generating reusable test components to test software applications. The computer-implemented method for generating reusable test components to test software applications may comprise: accessing an object model relating to at least part of a software application; and generating at least one test component applicable to test the software application, comprising: analyzing the object model, generating a meta-description from the object model and store the meta information in at least one descriptor according to a meta model, and generating the test component and a corresponding component implementation based on the descriptor.

Abstract: Embodiments of the invention provide systems and methods for analyzing memory heap information for investigation into a memory leak caused by an application. According to one embodiment, a method of analyzing heap data can comprise obtaining the heap data from a memory. The heap data can represent a plurality of objects of one or more classes, each object identifying a referrer instance, a field in the referrer, and a referent instance. A statistical analysis can be performed on the heap data to identify objects within the heap that are contributing to a growth of the heap. The heap can be traversed based on the referrer instance of one or more objects identified as contributing to the growth of the heap to a root object identified as not contributing to the growth of the heap.

Abstract: A method, system and program product for recording a program execution comprising recording processor context for each thread of the program, results of system calls by the program, and memory pages accessed by the program during an execution interval in a checkpoint file. Processor context includes register contents and descriptor entries in a segment descriptor table of the operating system. System calls are recorded for each program thread, tracked by an extension to the operating system kernel and include returned call parameter data. Accessed memory pages are recorded for each program process and include data, libraries and code pages. The program address space, processor context, and program threads are reconstructed from checkpoint data for replaying the program execution in a different operating system environment.

Abstract: An electronic device includes a registered jack 45 (RJ45) port, a network card, a universal asynchronous receiver/transmitter (UART), and a chip. The RJ45 port includes two receiving signal pins, two transmitting signal pins, a data transmitting pin, and a data receiving pin. The network card is connected to the two receiving signal pins and the two transmitting signal pins. The UART includes a data receiving pin and a data transmitting pin. The data transmitting pin is connected to the data receiving pin. The data receiving pin pin is connected to the data transmitting pin. The chip is connected to the UART. The UART is operable to debug or software-update the chip according to signals transmitted through the data transmitting pin and the data receiving pin.

Abstract: Software in an electronic device can be tested using a combination of random testing and deterministic testing. In various embodiments, deterministic tests can run for a prescribed duration and/or a prescribed number of iterations before and/or after random testing. Test results can be weighted using a metric representing an amount of code that was stressed during testing. This metric can be determined by tracking software code that is loaded into memory during testing.

Abstract: Cloud computing platforms having computer-readable media that perform methods to generate debuggable dump files are provided. The cloud computing platform includes at least one server having a host virtual machine, guest virtual machine, and hypervisor. The host virtual machine receives a command to generate the debuggable dump file. In response, it suspends all virtual processors executing on the guest virtual machine. The memory pages of the suspended virtual machine are written into a debuggable dump file, and the suspended processors are resumed at an appropriate time.

Abstract: Cloud computing platforms having computer-readable media that perform methods to generate debuggable dump files are provided. The cloud computing platform includes server devices running operating system kernels. Optionally, the server may include a hypervisor. The operating system kernel receives a command to generate a debuggable dump file. In response, the operating system estimates memory requires to store the requested memory pages, allocates an appropriately sized buffer, and freezes computation. A hypervisor is present and if its memory pages are requested, the hypervisor freezes its computation. The hypervisor stores its memory pages in the buffer and resumes computation. The operating system kernel stores its pages to the buffer in priority order and resumes its computation. The contents of the buffer are written out as a debuggable dump file.

Abstract: The disclosure presents categorization of users into groups comprising expert users and novice users. A system and method analyzes the users' inputted data in helpdesk troubleshooting software to determine the deviation of novice users from expert users, or the deviation of novice users to a preconfigured behavior as determined by management policy. Other embodiments are also disclosed.

Abstract: A computerized method, program product, and a service that allocates and isolates leaky memory during the execution of an application in a data processing system. A memory controller having several components first identifies a leaky section of memory and delegates to an allocation component to allocate more memory if possible. If, however, the problematic memory section should not be allocated more memory, an isolator component can isolate the memory section and further divide the memory section into subsections and so on. Each section and each subsection may then be tested to determine if more memory can be allocated, tested to determine if memory resources are strained so as to identify the application or its component causing the strain and then binding the memory. Each section and subsection and further divided and isolated until the leaky portion of memory is identified, and as a result, the software component causing the leak can also be identified.

Abstract: There is provided a system and method of providing program tracking information. An exemplary method comprises compiling a program into a plurality of instruction bundles. The exemplary method also comprises placing an instruction to store program tracking information in a local path table or a global path table into at least one of the plurality of instruction bundles.

Abstract: A portable executable file can be repaired by identifying an invalid field of a portable executable file. A likelihood of repairing the invalid field of the portable executable file is determined. A repair model for repairing the invalid field of the portable executable file is generated, and the invalid field of the portable executable file is repaired based upon, at least in part, the repair model.

Abstract: A system and method for debugging a running process of an application or component is disclosed. A debugging client has a user interface for receiving user commands to configure and control a debugging program. A debugging agent is resident in a local network area with the running process and has a direct connection with the running process. The debugging agent is configured to execute the debugging program to obtain debugging information on the running process, and to send the debugging information to the debugging client. A Web services communication link is established between the debugging client and the debugging agent for communicating signals to the debugging agent from the debugging client representing the user commands to configure and control the debugging program.

Abstract: A system and method for identifying modeling errors in textual use case description analyze an input text describing a use case and create an application model representing the use case, the application model containing information obtained from analyzing the input text describing the use case. The application model may be automatically analyzed using automatic process and one or more errors in the use case and/or reports about the use case may be generated. In one aspect, processing components may be integrated into a user development environment to allow developing use cases and improving them incrementally and/or iteratively as information is identified about the use cases.

Abstract: An apparatus (100) in an example comprises a test-script generator (704) and selection logic (114). The test-script generator (704) serves to create a test script (116) through identification of currently-available elements (604, 606, 608, 610, 612, 614, 616, 618) of an application (106) under test. The test script (116) is employable to exercise the application (106). The selection logic (114) serves to identify elements (406, 408) of a currently-executing component script (402) within the test script (116), contemporaneous with execution of the test script (116), that may be affected by graphical user interface changes made to the application (106). The identification of the elements (406, 408) of the currently-executing component script within the test script (116), contemporaneous with execution of the test script (116), that may be affected by the graphical user interface changes by the selection logic is contemporaneous with the exercise of the application (106) by the test script (116).

Abstract: Behavior Request is passed by a behavior injection harness specifying a particular behavior point, component, configuration or machine state, iteration (or sequence) to execute, product-independent atomic operation or to send data to be consumed by product code. Behavior requests can be configured and passed to a product process during runtime to change the state of a thread without affecting rest of deployment or configuration.

Abstract: A method for processing the volume of information handled during the debugging phase of an operational software onboard an aircraft includes: dividing the execution path of the operational software into functional intervals by placing progression points at each function of the program; placing control points associated with each progression point; normal execution of the program that includes: storing the execution state of the program at the location of each progression point, wherein the storage of an execution state results in the suppression of the execution state previously stored for said progression point; upon the detection of an error, searching the progression point corresponding to a faulty function; searching for a software start execution state; regenerating the start execution state; correcting the error in the faulty function; and re-executing the program.

Abstract: Provided are a software reliability test method using selective fault activation, a test area restriction method, a workload generation method and a computing apparatus for testing software reliability using the same. The software reliability test method registers a test target module. The software reliability test method injects a fault into a fault injection target function when a caller of the fault injection target function is included in the registered module, in a case of calling the fault injection target function.

Abstract: Systems and methods are disclosed to detect an error in a software with a computer readable code by applying a modular analysis based on the principle of structural abstraction and refinement of program structure; and detecting an assertion violation indicative of a software bug.

Abstract: A software testing system includes a test interface and a verification interface. The test interface receives a first processing request for the application program under test. The test interface generates a second processing request equivalent to the first processing request, and communicates the first and second processing requests to the application program under test and a model of the application program, respectively. A verification interface compares a first and a second response data set received, respectively, from the application program under test and the model. The verification interface generates an error indication if a difference is determined from the comparison of the first and second response data sets. If a difference is not determined from the comparison, then the verification interface generates a success indication. The verification interface communicates either the success or error indication to the test interface.

Abstract: A method for detecting security intrusions and soft faults in a software system includes receiving a multi-dimensional performance signature built from operating system metrics sampled by a software system monitoring infrastructure, associating a plurality of buckets with each component of the performance signature, comparing a component of the sampled performance signature to an expected value for the performance signature component, where a bucket for the performance signature component is incremented if the sampled performance signature component exceeds the corresponding expected value, and the bucket for the performance signature component is decremented if the sampled performance signature component is less than the corresponding expected value, executing a security alert notification when the bucket for the performance signature component exceeds a first threshold, and executing a soft-fault notification when the bucket for the performance signature component exceeds a second threshold, where the first

Abstract: Embodiments of the invention are associated with an application process that comprises multiple threads, wherein threads of the process are disposes to run on a data processing system, and each thread can have a user mode or a kernel mode machine state, or both, selectively, when it is running. An embodiment directed to a method comprises the steps of allocating a specified memory location for each of the threads, and responsive to a given thread entering a sleep state, selectively saving the kernel mode machine state of the given thread in the specified memory location for the given thread. The saved machine state comprises the state of the given thread immediately prior to the given thread entering the sleep state. In response to detecting a hang condition in the operation of the process, a debugger is attached to the process to access at least one of the saved user mode machine states.

Abstract: Methods, systems, and computer-readable media for expressing fault correlation constrains to a developer of a service application are provided. Initially, the fault correlation constraints are identified by inspecting an architecture of resources comprising a data center. Based on the resources, sets of nodes that become concurrently unavailable due to a failure mode or update scheme are aggregated. These fault correlation constraints, upon being communicated to the developer, then may be incorporated into a service model produced thereby. Accordingly, the service model is tailored to the specific characteristics of the data center and is provided with instructions as to how to partition instances of the service application throughout the distributed resources of the data center. Thus, the fault correlation constraints provide a developer with insight into rules and structures on which the data center is constructed and assurances of a certain level of fault tolerance upon deploying the service application.

Abstract: An apparatus and method for testing a digital device or software installed in the digital device are provided. According to one aspect, the apparatus for testing the digital device or software installed in the digital device includes a test agent for providing a test execution environment, and the test agent performs a test for each test case in response to a command from a test director. The test agent may report an execution state of the test to the test director, and the test director may generate a test result report based on the report or resumes the test upon generation of error.

Abstract: Process reflection techniques are described in which a reflected process is created to facilitate analysis of a process. Events are detected to initiate reflection of a target process. Process reflection of a target process may be initiated by an external process or by the target process itself. A reflected process of the target process is created. In an implementation, data defining the target process is replicated, copied, or otherwise collected from the target process to create the reflected process. Then, analysis may be performed on the reflected process while execution of the target process continues.

Abstract: A method of stealthily debugging software comprises dynamically injecting a jump into an executing target program; performing a debugging operation on the target program; and dynamically removing the injected jump from the target program. Dynamically injecting a jump comprises copying memory contents from a selected breakpoint location to a second memory location, and writing a jump instruction and location at the breakpoint location. Dynamically removing the injected jump comprises copying memory contents back to the breakpoint location from the second memory location. The method may further comprise replacing a pointer to a system function with a pointer to a debug module in a syscall table, and placing the debug module in a slack space of the target program. A debugging system is also disclosed.

Abstract: An apparatus and method are provided for performing integrity checking of software code executing on a processing unit of the apparatus. The apparatus further includes debug logic used when debugging program code executed by the processing unit, and trusted logic for performing trusted integrity checking operations on less-trusted program code executed by the processing unit. The debug logic has an interface via which the trusted logic can program one or more control registers, that interface not being accessible by the less-trusted program code. The trusted logic programs the control registers so as to cause the debug logic to be re-used to detect one or more activities of the processing logic during execution of the less-trusted program code, and the trusted integrity checking operations performed by the trusted logic are influenced by the activities detected by the debug logic.

Abstract: A hand-held electronic device having a remote control application user interface that functions to displays operational mode information to a user. The graphical user interface may be used, for example, to setup the remote control application to control appliances for one or more users in one or more rooms, to perform activities, and to access favorites. The remote control application is also adapted to be upgradeable. Furthermore, the remote control application provides for the sharing of operational mode information.