home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Mega Top 1
/
os2_top1.zip
/
os2_top1
/
DOS_GG
/
COMCAT
/
VOL95.ARJ
/
VOL9508
< prev
next >
Wrap
Text File
|
1992-01-07
|
3KB
|
67 lines
O S / 2 - P r o g r a m m a T h e e k volume 9508
Source: BBS's
Titel: Multiscope Debugger demo
Number Name Size Date Comments
CATALOG O08 320 9-20-89 This list
9508.01 EXTRACT2 EXE 24447 7-28-89 Short OS/2 UnZIPper
9508.02 INSTALL CMD 26 7-28-89 Batch file to run ^
9508.03 MS-DEMO ZIP 326691 7-28-89 MultiScope debugger demo
VOL9508 ABS 2078 9-20-89 Disk abstract by Z.
6 File(s) 2048 bytes free on volume DOSGG9508
MultiScope is a programmer's tool that lets you find and diagnose
programming errors. Programmers usually follow three basic steps
when debugging a program:
* Finding an error.
* Diagnosing an error.
* Fixing an error.
The first step in the debugging process is to find the errors in
your program. It is a common for beta testers or quality assurance
personnel to test your program to help find errors. The testers
prepare "bug reports" detailing the program errors. However,
diagnosing the problems that led to the errors is not always
possible.
The second step in the debugging process is diagnosing the cause of
the error. Errors are common during software development and may
take many hours, and sometimes days, to properly diagnose. Often
errors happen the first time you test your program, but many times
they arise only after repeated testing. If your program terminates
abnormally (crashes) diagnosing the cause of the crash can be
difficult if not impossible.
With MultiScope it is easy to find and diagnose errors
because you can
* Control the execution of your program.
* Inspect your program in easy to understand views.
* Pinpoint the location of errors at the source code level.
The final step of the debugging process is fixing your program.
Although MultiScope can make the first two steps of the debugging
process easier, it cannot fix your program's errors. How you fix
these is up to you.
Mechanisms that Multiscope provides:
* Execute your program in steps.
* Look at your program's modules.
* Examine your program's source code.
* Browse through your program's data structures.
* Modify a variable.
* View a graphic data representation.
* Set simple and conditional breakpoints.
* Look at your program's memory.
* System Requirements
o IBM XT/286, AT, PS/2 model 50, 60, 70, 80 or 100% compatibles
o OS/2 Standard Edition 1.1 or Extended Edition 1.1
o One high density diskette drive and hard disk