Don't you have to include the BOUNDS statement in $CONTROL
in order for the debugger to give you a statement number ?

HTH

David Burney                                                Summit Racing
Equipment
[log in to unmask]                 http://www.summitracing.com
----------------------------------------------------------------------------
----------
                               AXE ME ABOUT EBONICS.
----------------------------------------------------------------------------
----------
All opinions expressed herein are mine and in no way reflect those of my
employer.



> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Born, Ken
> Sent: Friday, May 11, 2001 10:11 AM
> To: [log in to unmask]
> Subject: Debug Analysis from Abort process
>
>
> Greetings,
> I remember a long time ago that you can determine what line
> in the program
> blew up by the following:
> **** Bound violation or range error (TRAPS 12).
>
> ABORT: ALLDIN.RUN.ALERTS
>      PC=9dc.00012468 format_leads_message+$90
> * 0) SP=41846b10 RP=9dc.000125a0 handle_msgf+$4c
>   1) SP=41846a90 RP=9dc.000126fc read_files+$d4
>   2) SP=418462d0 RP=9dc.00012a70 _start+$10c
>   3) SP=41846250 RP=9dc.00000000
>      (end of NM stack)
>
> Usually, I could go to the procedure format_leads_message and
> determine
> where my bound violation occured.  But, viewing the mystery
> numbers, can I
> determine what line actually blew up?  what variable caused the bound
> violation?
>
> Thanks...
>
> * 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 *