T.R | Title | User | Personal Name | Date | Lines |
---|
4962.1 | system space | HOTRDB::LASTOVICA | Is it possible to be totally partial? | Sat Jan 25 1997 17:11 | 4 |
| an S0 indication means that the address is in VMS system space (those
addresses at 80000000 and above). You can generally use SDA on the
system where the failure occured to determine what code in VMS contains
the offending address.
|
4962.2 | | M5::LWILCOX | Chocolate in January!! | Mon Jan 27 1997 10:10 | 13 |
| <<< Note 4962.1 by HOTRDB::LASTOVICA "Is it possible to be totally partial?" >>>
-< system space >-
>> an S0 indication means that the address is in VMS system space (those
>> addresses at 80000000 and above). You can generally use SDA on the
>> system where the failure occured to determine what code in VMS contains
>> the offending address.
Thanks, Norm. To go a little farther, would it be accurate or inaccurate
to say then that the exception was not the result of an Rdb failure, but
that VMS had some problem and Rdb's reaction to that VMS problem was a bugcheck?
Liz
|
4962.3 | | HOTRDB::LASTOVICA | Is it possible to be totally partial? | Mon Jan 27 1997 10:55 | 6 |
| I don't think that explaination would be correct in all cases. You
need to determine where and why the accvio happened to have any idea if
it is an Rdb problem or a VMS problem. For example, if the accvio
happened in DECCRTL (perhaps installed /RESIDENT on an Alpha system)
and Rdb had passed a bogus parameter to some C function, then it would
likely be an Rdb bug.
|
4962.4 | Thanks! | M5::LWILCOX | Chocolate in January!! | Mon Jan 27 1997 11:23 | 5 |
| <<< Note 4962.3 by HOTRDB::LASTOVICA "Is it possible to be totally partial?" >>>
Thanks, Norm, that's what I needed to know.
Liz
|