HP3000-L Archives

March 2001, Week 4

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:
From:
EBEN YONG <[log in to unmask]>
Reply To:
EBEN YONG <[log in to unmask]>
Date:
Thu, 22 Mar 2001 15:57:55 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Hello,

I've noticed that there are instances where it is very easy to pinpoint the
source of a program abend:

HPDEBUG Intrinsic at: 147.00282304 cob_trap.print_message+$5ec
$$$$ Trap occurred at: _start+$a0, at Stmt    #59
     PC=292.000057d8 _start+$a0
* 0) SP=41842330 RP=292.00000000
     (end of NM stack)
$$$$ The variable 6 >   5 (limit)
============================================================

In the above example, the abend occurred at Statement #59.  Recompiling the
program yields this very clearly:

 00059 EY010322 028008    move 7 to x(y)

However, when faced with an HPDEBUG message like the one below, how do I
read the Trap message to pinpoint the location of the error?

HPDEBUG Intrinsic at: 104.0026d304 cob_trap.print_message+$5ec
$$$$ Trap occurred at: screen$008$+$3ed4, at ????
     PC=3bb.0006530c screen$008$+$3ed4
* 0) SP=418529f0 RP=3bb.00000000
     (end of NM stack)
$$$$ The variable 10 >   9 (limit)

Thanks,

Eben Yong
Health Plan of San Mateo

ATOM RSS1 RSS2