[1188] in testers

home help back first fref pref prev next nref lref last post

new console

daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Sun Nov 25 15:52:55 1990

To: testers@ATHENA.MIT.EDU
Reply-To: marc@MIT.EDU
Date: Sun, 25 Nov 90 15:52:30 EST
From: Marc Horowitz <marc@ATHENA.MIT.EDU>

I just ran /mit/xdm/install-test this afternoon on podge, a pmax in
the sipb office.  I got a black bar console message, so I knew
something was wrong.  I tried running a new console:

<24> podge:~> /afs/athena/astaff/project/xdm/@sys/bin/console
console: Couldn't load /mit/adt/src/console.ad
Segmentation violation (core dumped)

This may be the wrong way to start a new console, but it is the
intuitively obvious way.  And in any case, it shouldn't be dumping
core.  BTW, using the invocation in the dm-config file, it doesn't
dump core.  Since I don't know where a version with symbols is, I
can't give you a stack trace.  The core dump is in
podge:/usr/tmp/core.console until the system deletes it.

I tried using config_console.  The old console process dies, and the
new one restarts, but it doesn't seem to help.  I still get black
bars.

(time passes....)

I just spent a lot of time groveling around.  The right way to get
console output is to read from /dev/xcons (thanks to Ezra for that).
Some #ifdef ULTRIX code in dm/dm.c to open and dup the right thing
onto fd 0 should make the console happy.  For now, running console <
/dev/xcons seems to win (as long as you give it a -f arg so it doesn't
dump core).

		Marc

home help back first fref pref prev next nref lref last post