Problematic binary isolator

Details Problematic binary isolator Problematic binary isolator

2000-12-13

2003-12-30

Das, Chameli C. (Department: 2122)

Data processing: software development, installation, and managem

Software program development tool

Testing or debugging

C717S126000, C717S127000, C717S128000, C717S129000, C717S130000, C714S038110, C714S048000, C714S052000, C709S241000

Reexamination Certificate

active

06671873

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates generally to computer program compiling and debugging, and more specifically to an automated system for determining the file or set of files that cause a program run-time failure and/or performance problem when complied with a particular compiler, or compiled in a particular manner.
BACKGROUND
The need for computer programs with greater functionality is increasing dramatically and with added functionality of computer programs comes added complexity. It is not uncommon today for a computer program to contain hundreds or even thousands of source code files. Computer program compilers are used to transform these source code files to machine-readable files (e.g., executable files). There are many varieties of compilers available for different languages and from different manufacturers. Often times a computer programmer may wish to take a set of source code files already compiled on one type of compiler and compile the same source code files on another interoperable compiler. This may be desirable to realize the benefit of some advantage which one compiler has over another, for example greater speed or additional optimization features.
A computer programmer may find that the set of source code files that compiles and runs successfully using one compiler may not execute properly when compiled with another one. That is, the executable program produced using one compiler runs fine and the executable program produced using another compiler crashes for the same set of source code files. Alternatively, the programmer may find that the set of source files compiles using one set of compilation options and does not compile with a different set of options. Typically the problem is caused by one source code file or the interaction of two or more source code files. The vast majority of the source code files will usually present no difficulty using either of the two interoperable compilers. The problem may be due to the source code itself or some unknown deficiency in the compiler. It may be possible and desirable to compile all of the source code files except the problematic file(s) on a preferred compiler and compile the problematic file(s) using a compiling environment that does not cause a problem.
To do this a computer programmer may need to determine which source code file or set of files is problematic. This process typically involves creating test executable programs made up of some source code files compiled using the functioning compiling environment and some source code files compiled using the problematic compiling environment and determining if the produced executable file runs properly. Through iterations of this process the computer programmer may be able to isolate the problematic source code file(s). This process requires a great deal of effort on the part of the computer programmer. The computer programmer must decide which set of files will be used to construct the test executable program and must determine if the test executable program experiences a failure or degradation in performance. The computer programmer, typically, may monitor the evaluation process and make decisions for each iteration of the debugging process.


REFERENCES:
patent: 4694420 (1987-09-01), Pettet et al.
patent: 4696007 (1987-09-01), Moriyama
patent: 5175856 (1992-12-01), Van Dyke et al.
patent: 5742754 (1998-04-01), Tse
patent: 5966541 (1999-10-01), Agarwal
patent: 6178548 (2001-01-01), Hickman et al.
patent: 6226786 (2001-05-01), Hickman et al.
patent: 6305010 (2001-10-01), Agarwal
patent: 6378087 (2002-04-01), Flanagan et al.
patent: 6418444 (2002-07-01), Raduchel et al.
patent: 6560757 (2003-05-01), Ballam
patent: 6601114 (2003-07-01), Bracha et al.
patent: 6601203 (2003-07-01), Asano et al.
TITLE: Abstract debugging of higher-order imperative languages, author: Bourdoncle, ACM, 1993.*
TITLE: Compiling a Functional Language, author: Cardelli, ACM, 1984.*
TITLE: Recovery of Jump Table Case Statements from Binary Code, author: Cifuentes et al, IEEE, 1999.*
TITLE: Binary Translation, author: Sites et al, ACM, 1993.

Affiliated with

Also associated with

Rating

Problematic binary isolator does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Problematic binary isolator, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Problematic binary isolator will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3179794