HP3000-L Archives

May 2001, Week 2

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Debug Analysis from Abort process
From:
"Born, Ken" <[log in to unmask]>
Reply To:
Born, Ken
Date:
Fri, 11 May 2001 09:11:12 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines) 
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 *

ATOM RSS1 RSS2