Start reading the stack trace bottom - up. Assuming you
have the source of the problem program, you'll find
familiar looking function names calling each other.
This should already give a fair idea where the problem
occurs. If you don't see what the problem is, you can
run the program inside a debugger and put a breakpoint
at get_bool for example and go from there

HTH

Johan

----- Original Message -----
From: "Satheesh Kalam" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, 25 November, 2004 5:50
Subject: [HP3000-L] "dbg_stackdump_cmds" erron in a PASCAL program


> Hi
> While running a PASCAL program I'm getting the following ABORT message.
> I'm struggling to find a solution for the same.
> Anticipating some help on this issue.
>
>
> ABORT: XXXXXXP.XXXX.XXXX
>       PC=a.00fdc02c dbg_stackdump_cmds+$30
> NM* 0) SP=41acd430 RP=a.009aacc4 trap_handler.handle_setdump+$f0
> NM  1) SP=41acd3b0 RP=a.009ac008 trap_handler+$3f8
> NM  2) SP=41acd330 RP=a.0037886c QUIT+$d4
> NM  3) SP=41acccb0 RP=a.00378764 ?QUIT+$8
>         export stub: 2e5.00e5f0a8 QUIT+$258
> NM  4) SP=41accbf0 RP=2e5.00e5ee14 ?QUIT+$8
>         export stub: 381.00025ce0 write_to_error_file+$2e4
> NM  5) SP=41accb70 RP=381.00025f98 abort_pro+$40
> NM  6) SP=41acc870 RP=381.000277cc get_bool+$3d4
> NM  7) SP=41acc570 RP=381.0002c9e0 get_emp_info+$2dc
> NM  8) SP=41acc4f0 RP=381.00031bbc process+$738
> NM  9) SP=41acc430 RP=381.000352fc PROGRAM+$158
> NM  a) SP=41acb1b0 RP=381.00000000
>     (end of NM stack)
>
>
> Thanks and Regards
> Satheesh Kumar.
>
> * 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 *