Re:
> 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)

Assuming this isn't SPLash! (compiled with $STMT, which inserts real line
numbers), you'll need to get a compiler listing.

Assuming Pascal, try:

   $code_offsets on$

and optionally:

   $statement_number on$

                          format_leads_message

        STMT  OFFSET      STMT  OFFSET      STMT  OFFSET
           1       0         2      28         3     100

The above would made-up values indicate that the abort happened at
"statement" 2 (because format_leads_message+$90 is >= offset $28,
and < offset $100)

The compiler listing would show what statement is statement 2.

If you add $statement_number on$, your code will slow down a small
amount (1 to 6 percent, on average), but Debug will show you
statement numbers (not line numbers!) as "Stmt 2" when you do
a "DC" command, or show the NM code window (WON command).



Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

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