HP3000-L Archives

May 1997, 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:
Goetz Neumann <[log in to unmask]>
Reply To:
Date:
Wed, 28 May 1997 20:02:38 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Jens von Bulow wrote:
>
>         The error message on the HP3000 console was as follows.
>
>                         system abort 1458 from subsystem 102
>                         system halt 7, $05B2
>

This is the most 'generic' system abort we have in the MPE/iX OS.
It basically means that a processes encounters any kind of trap,
at a point in its execution where it is set to the critical state.

OS routines (and subsystems like networks, etc) do this per a
call to the OS internal (no Intrinsic !) routine SETCRITICAL,
with its purpose to hold of any interrupts (like e.g. a
termination interrupt from an ABORTJOB or KILL) during the
execution of a 'critical' piece of the execution.

Now if your program does not call SETCRITICAL, then one of the
OS or network procedures that your program called probably
encountered a trap. This could be due to an invalid parameter
or pointer passed to the OS routine, though mostly the latter
do a good job of parameter checking.

Generally a user mode program (unless your program uses PRIV
mode) should not be able to crash the system, so this sounds
like a case where you should involve your local Response Center.

hope this helps,

Goetz (normally @hp.com).

ATOM RSS1 RSS2