Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Watcom Debugger Guide - the linker is the tool that puts together a complete program and sets up the http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
The linker is the tool that puts together a complete program and sets up the
debugging information for all the modules in the executable file.  There is
a linker directive that tells the linker when it should include debugging
information from the modules.

For "Dwarf" format debugging information, the directive is:

DEBUG DWARF

For "Watcom" format debugging information, there are two levels of debugging
information that you should collect during the link.  They are:

DEBUG WATCOM LINES
    global names, source line numbers

DEBUG WATCOM ALL
    global names, source line numbers, local variables, typing information

Linker DEBUG directives are position dependent so you must make sure that
the directive precedes the object files and libraries that require debugging
information.

For instance, if the file "mylink.lnk" contained:


     #
     # invoke with: wlink @mylink
     #
     file main
     debug watcom lines
     file input, output
     debug watcom all
     file process

then the files input and output will have global names and source line
information available during debugging.  All debugging information in the
file process is available during debugging.  No information is available for
main except global names.

If you use a DEBUG directive anywhere, all files, including main, will have
global name information.

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson