On 2011-11-12 16.41, Oleg Safiullin wrote:
Huh. At what point? That should not happen. I don't see anything like
that when I try to log in as guest...
Just got the same error when i tried to log in as guest using SET HOST.
No problems for telnet login.
[...]
Oh! Darn! I bet I know what the problem is with that... The normal terminal driver only
requires read access to the buffer that is used to write to the terminal. The RT: device
driver, which is what is used for the CTERM, probably wants write access, even though it
will only read from the buffer.
And then PIP (which is what TYPE invokes) does a QIO from a memory buffer that is read
only... Not sure I can do anything to fix that... :-(
I'll test and check some more...
(I consider the write access check a bug in the device driver, and I've stumbled on it
before when writing my own code...)
Johnny
--
...
$ @LB:[1,2]SYSLOGIN.CMD
What is your name? GHJ
RSX-11M-PLUS BL87mP (MIM ) 1292K PDP-11/74 at 16:37:59.5, 12-NOV-11
Users=7 Idle=100% Task=.IDLE. Up: 28 days, 21:56. Ticks=0 Errseq=15.
user task uic pri where state size(K) ioc par
GHJ AT.R0 * [ Self ] 64 RT0 Stopped 4/23 GEN
Johnny DTRT10 [ Self ] 50 TT10 Stopped 13/64 (1) GEN
J Billquist DTRT6 [ Oper ] 50 _TT6 Stopped 13/64 (1) GEN
GHJ WHOR0 * [ Self ] 50 RT0 Running 1/4 GEN
J Billquist (In MCR) [ Oper ] _TT4
J Billquist (In MCR) [ Oper ] _TT5
J Billquist (In MCR) [ Oper ] _TT7
J Billquist (In MCR) [ Oper ] _TT11
16:38:01 Task "TYPR0 " terminated on processor "A"
Memory protect violation
R0=000472
R1=027200
R2=000000
R3=000000
R4=001404
R5=000022
SP=000432
PC=147620
PS=070004
$