Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Blinker 5.10 Online Reference - <b> approaches to debugging</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 Approaches to debugging
------------------------------------------------------------------------------
 Usually link time errors are well identified and the approach to their
 resolution is given in the individual error message descriptions in the
 following section. Some additional techniques for discerning link time
 problems include using:

 . The VERBOSE link script command, to see what Blinker is doing when
   an error occurs.

 . The MAP command, to see how the .EXE has been constructed.

 . The ECHO command, to output your own messages from within the link
   script.

 Runtime error conditions which arise from the linking process can be more
 difficult to diagnose and resolve.
 When encountering problems which do not appear to be attributable to the
 code itself or to other factors in the environment, the following steps are
 suggested in analyzing the linker's role in the problem.

 1. Ensure that the program stack is sufficiently large by increasing the
 value specified with the STACK nnnn or BLINKER PROCEDURE DEPTH nn commands.

 2. Check for duplicate modules using the BLINKER MESSAGE DUPLICATES command.
 See the online help for the definition of this command. Usually this
 situation can be resolved by altering the order of the libraries and, if
 necessary, using the MODULE FROM command.

 3. Attempt to recreate the problem in a small test program, or attempt to
 isolate a small portion of the program which produces the error by
 repeatedly removing references to code which is not executed and then
 re-linking.

 4. Attempt to test the original program and the smaller test program with
 another linker. If the problem does not occur, retry Blinker with the same
 files and order of libraries as the other linker.

 5. Contact Blinker technical support via our Web site at www.blinkinc.com.
 The Technical Support section has our latest program updates and technical
 reports. Please refer to these before sending an email message or calling
 our technical support line. Also, review this manual for additional
 information. If you should call, please have your Blinker serial number,
 link script files and the exact text of the error message at hand.

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