1) If you don't have :SETDUMP turned on, do so.
2) You can compile the C program with options to produce a listing containing line-number/address offset information.
3) With the stack trace from :SETDUMP, you should be able to locate the line where the failure is occurring.

Unfortunately, XDB can't be used to debug subprograms (well, it can, but the required self-flagellation makes it effectively impossible), so you'll probably have to do your debugging with printf()s.

If the data used by the failing code is generated within the C program, that's where you'll concentrate your efforts. If the data is passed by the COBOL program, you can build replacement modules that you can substitute for the called C program, modules which can provide expanded information on passed parameters, write data to files, etc.

If you come back with the results of the steps above, we might be able to offer additional suggestions.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *