[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Zap Technical Conference |
| Notice: | ZAP Version 5.3 is available. See note 1.1 |
| Moderator: | ZAPDEV::MACONI |
|
| Created: | Mon Feb 24 1986 |
| Last Modified: | Mon May 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 170 |
| Total number of notes: | 492 |
16.0. "Problem with WHO" by SPYDER::BARKER (The Lonely Goatherd) Thu Jun 12 1986 12:57
We've found WHO a nice little utility. I seem to remember that I wrote something
similar in DCL a year or two ago to display this sort of information.
The problem is that it crashes 50% of the time when you attempt to run it. I
cannot find any pattern to it. You can run it successfully & then try again a
couple of minutes later when this time it will crash. This is without logging
out.
I've got it installed so that all users can access it. Our configuration is a
780 running VMS 4.2.
I'd appreciate any help as it's a bit irritating to have a utility that randomly
crashes.
Nigel Barker
The following is the result when WHO decides to crash:-
$ mc who
[Who: System process summary at 12-jun-1986 16:23:22.29, Version 2.1]
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000084, PC
=00000C80, PSL=03C00004
Improperly handled condition, image exit forced.
Signal arguments Stack contents
Number = 00000005 00000000
Name = 0000000C 00000000
00000000 00001578
00000084 27FC0000
00000C80 7FF6E9CC
03C00004 7FF6E9B0
00000612
0000000F
7FFA6839
7FFE640C
Register dump
R0 = 000181F0 R1 = 00019900 R2 = 000199F0 R3 = 00000000
R4 = 00000000 R5 = 000187F0 R6 = 00000000 R7 = 00000002
R8 = 0000000C R9 = 00018EA2 R10= 00019AB0 R11= 7FFE33DC
AP = 7FF6E904 FP = 7FF6E8C4 SP = 7FF6E940 PC = 00000C80
PSL= 03C00004
$
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 16.1 | Known bug | MRMFG3::K_MACONI | The Doctor | Mon Jun 16 1986 10:03 | 8 |
| The WHO utility uses linked lists to generate the report which is
displayed on the users terminal. Unfortunately, the program can
become confused and it falls off of the end of one of the lists
when certain conditions exist on the system. This causes the
extremely irritating crash which seems to randomly occur.
Currently, I am trying to stop this from happening by putting more
checks into the program. I hope to have this behavior fixed soon.
|