Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site allegra.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!karn
From: karn@allegra.UUCP (Phil Karn)
Newsgroups: net.bugs.4bsd,net.bugs.uucp
Subject: uucico hangs
Message-ID: <2393@allegra.UUCP>
Date: Tue, 10-Apr-84 12:39:52 EST
Article-I.D.: allegra.2393
Posted: Tue Apr 10 12:39:52 1984
Date-Received: Wed, 11-Apr-84 05:44:42 EST
Organization: Bell Communications Research, Inc
Lines: 13

For some time now, uucico has often gotten stuck on allegra when calling
out to other sites. Typically, it will wait indefinitely on a modem
open call, or on a read call once the connection has been established.
In doing stack traces of the code once the stuck process has been killed
and dumped, the code preceeding the offending open or read appears to
set alarm timeouts properly. Furthermore, the code doesn't ALWAYS fail;
I've watched it many times handle timeouts from non-answering systems
just as it should.  It's just that alarm signals occasionally get lost.

I am therefore wondering if there are some fleeting bugs in the way
alarms, signals and/or setjmp/longjmp are handled in 4.2. Any ideas?

Phil