|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
STATIC DEBUGGING TOOLS
Tool #1 - Jtest
What is Jtest? ...
• Eliminates crash-causing problems
• Ensures that code is structurally sound
• Prevents simple errors from becoming more serious problems
• Reduces time spent on code reviews and debugging
• Prevents errors from returning to code
• Accelerates learning curve for the Java language
• Ensures that classes behave according to specifications
• Streamlines development process for quicker time to market
Tool #2 – Insure++
Insure++ is a powerful tool that can help you develop "Total Quality Software. ...
Insure++ includes three distinct tools that work together to improve your development process. ...
Insure++ - Automatic Runtime Debugging
Insure++ finds a wide variety of programming and memory access errors including:
• Memory corruption due to reading or writing beyond the valid areas of global, local, shared, and dynamically allocated objects. ...
DYNAMIC DEBUGGING TOOLS
Tool #1 - DDT
DDT – Dynamic Debugging Tool
DDT is used to debug programs written in assembly language. ... com save customized command program
DDT{ fileref}
The DDT command initializes a debugging session. ...
Tool #2 - FDEBUG
FDEBUG - a dynamic debugging tool. ...
call fdebug
call fdebug( di )
call fdebug( di, do )
Where:
di
is the logical unit from which to read debugging requests. ... To get a traceback again, you must first use the MA, FU or SU request to reestablish the debugging context, then hit carriage return again. ... FDEBUG requests can be planted by supplying debugging requests on logical unit 44 using $DATA~44 or equivalent control cards. ... You turn it on with the TSS command
switch on=4
and turn it off by typing
switch off=4
Requests:
With some exceptions, debugging requests can be executed in one of two ways. ...
It should be pointed out that debugging of optimized programs may be complicated by the fact that the values of certain variables are often kept in registers rather than in memory. ...
To make debugging link overlay jobs less tedious, there is a system supplied subroutine of the form
SUBROUTINE LODLNK(LINK)
CHARACTER*6 LINK
1 RETURN
END
which is called by the LINK/LLINK overlay subroutine immediately after loading a link. ...
If the CAll request is used to call a debugging subroutine, break service is turned off.
Approximate Word count = 3603
Approximate Pages = 14.4
(250 words per page double spaced)
|
|
|
|
|
|