Alice,
When the program fails, there may be some more information and perhaps you
could post that? There are others on the list who are proficient in C and
COBOL who may also be able to help.

Do you have the source and could it be shared? Likely with the program
failure, it will specify in what routine (function) it failed and that would
be the interesting part of the source. C strings end with a NUL (COBOL
special name value 1) and may cause issues. What are you passing from COBOL?
How are those variables defined in COBOL and how are they filled with data
before the C routine call? How is the C function defined (what is it's
prototype)?

Greg Skvorak
Beechglen Development, Inc.

----- Original Message -----
From: "Alice Utter" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, October 05, 2001 10:22 AM
Subject: Debugging 'C' programs


> I am trying to debug a 'C' program, but I do not have much experience
> debugging 'C' on the HP.  The 'C' program is a subprogram called by a
> native mode COBOL program.  The program blows up erractically with an
'ieee
> overflow' message, which makes me suspect bad data in one of the
> calculations.  Could someone please offer some pointers on how to pinpoint
> the calculation, and how to verify the values that the calculation is
> using.  In the past we have tried using printf's to show the values,
> without any luck.
>
> Thank you,
> Alice Utter
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

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