Section 19.1: Coredumps Up Chapter 19: Debugging Section 19.3: All other errors 

19.2 Unexpected behaviour

If an application is failing in some way, the best thing to do is to create and examine (or ask those on the aubit4gl mailing lists to examine) a debug file.
This is created by setting
$ export DEBUG=ALL
You can then run your application and it should generate a file called ’debug.out’. This file can get huge very quickly, though only the last 100 or so lines will normally be needed to see whats wrong.
You may also find it useful to compile using the -g option and run it through the gdb debugger.
 Section 19.1: Coredumps Up Chapter 19: Debugging Section 19.3: All other errors