Browse Prior Art Database

Locate source code exception automatically in multi-language program

IP.com Disclosure Number: IPCOM000236158D
Publication Date: 2014-Apr-10
Document File: 4 page(s) / 412K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention uses system DUMP or lauguage environment DUMP combined with program compile list to inversely locate the exception in source code automatically in the multi-language program. When exception occurs, the DUMP records the exception function and statements with their offset off the exception function, even if the program consists of different subcomponents in different programming language. While the compile list generally has one or more compiled files, which record the offset of each source code line, each source file can be translated to the common assemble source whatever it is written in C, PLX, Java or COBOL language. Then the exception source code can be found by calculating the offset to the exception function. And the result will be highlighted dynamically. The users only need to input the DUMP to get exact exception source and the condition value for parameters in the exception. This will save users a lot of time in diagnosing the complex dump and locating the source code manually.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 4

Locate source code exception automatically in multi

Locate source code exception automatically in multi-

The complex multi-language programming probably consists of different complex (LE) language environment and such application is probably implemented by many subcomponents using different programming languages, such as C/C++, PL/I, COBOL, Java and assembler.

Up to the time, there is no good way to locate the source code exception on such complex platform, and the current platforms don't have a common dump analyzer that can support multiple programming language in such complex application.

The system dump or language environment dump, which can record even the multiple programming language, is the general diagnostic handling for most programming developers. But some program is always based on complex language environment and many core libraries with different components. So it is difficult to analyze the dump which contains much program runtime information. This will cost them too much time in tracking a minor bug on such complex platform. And it is difficult to collect the exception with general debug tool of other platforms. The language environment dump or other system dump can record the exception by specifying the dump option in source code.

Currently, the developers can only diagnose the reason manually on such complex multi-language program.

This invention uses system dump or language environment dump combined with program compile list to inversely locate the exception in source code automatically. When exception occurs, the dump records the exception function and statements with their offset off the exception function, even if the program consists of different subcomponents in different programming language. While the compile list generally has one or more compiled files, which record the offset of each source code line, each source file can be translated to the common assemble source whatever it is written in C, PLX, Java or COBOL language. Then the exception source code can be found by calculating the offset to the exception function. And the result will be highlighted dynamically. The users only need to input the dump with program compile list to get exact exception source and the condition value for parameters in the exception. This will save users a lot of time in diagnosing the complex dump and locating the source code manually.


a. System dump

Use LE run-time option to help obtain a system dump if an unhandled condition of severity 2 or greater occurs. These errors are the most common system dump we...