[11438] in Athena Bugs
sun4 7.6P: codecenter
daemon@ATHENA.MIT.EDU (alexp@MIT.EDU)
Mon Nov 29 13:30:25 1993
From: alexp@MIT.EDU
Date: Mon, 29 Nov 1993 13:29:56 -0500
To: Calvin Clark <ckclark@MIT.EDU>, bugs@MIT.EDU
Cc: alexp@MIT.EDU
Hi Calvin,
I am trying to track down some Codecenter bugs including a couple you
reported. The one about not recognizing "const" seems to have been
answered but if there is still a problem let me know. The one about the
occasional "Device busy" error is strange. I tried to make it happen on
davis and other machines, logged in both as myself and on a "generic"
test account, and never saw it in at least a dozen logins. Is it still
happening, and if so is there any pattern at all in what seems to cause
it? I asked around and apparently no one else seems to be running into
it. It might be that you have some initialization setting that triggers
it, but of course I have no way of knowing.
Alex Prengel, Jr.
ACS Software Acquisition Coordinator
>From ckclark@MIT.EDU Mon Nov 15 13:13:21 1993
>Received: by gregor.MIT.EDU (5.57/4.7) id AA12334; Mon, 15 Nov 93 13:13:16 -05>00
>Received: from DAVIS.MIT.EDU by MIT.EDU with SMTP
> id AA08704; Mon, 15 Nov 93 13:13:10 EST
>Received: by davis.MIT.EDU (5.0/4.7) id AA02268; Mon, 15 Nov 93 13:12:57 EST
>Date: Mon, 15 Nov 93 13:12:57 EST
>Message-Id: <9311151812.AA02268@davis.MIT.EDU>
>From: Calvin Clark <ckclark@MIT.EDU>
>To: bugs@MIT.EDU
>Subject: sun4 7.6P: codecenter
>Content-Length: 704
>
>-------
>System name: davis
>Type and version: SPARC/Classic 7.6P
>Display type: cgthree
>
>What were you trying to do?
> Start up codecenter.
>
>What's wrong:
> About half the time I try to start up xcodecenter,
> it brings up a separate white window with the
> message:
>
> Can't open /dev/pts/3: Device busy
> Failed to set /dev/pts/3 as our controlling tty!
>
> in it. I can use this window to type commands,
> but I would prefer if it were consistent and
> allowed me to type in the main window.
>
> All the time.
>
> There is probably some sort of race condition
> going on here.
>
>What should have happened:
> If it needs a pseudo-tty, it should get one.
>
>Please describe any relevant documentation references:
> N/A
>,p
>
