From owner-freebsd-questions@FreeBSD.ORG Sat Jun 12 17:18:06 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53E8B16A4CE for ; Sat, 12 Jun 2004 17:18:06 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 768F443D2D for ; Sat, 12 Jun 2004 17:18:05 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 198924B2 for ; Sat, 12 Jun 2004 19:17:52 +0200 (CEST) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96032-03 for ; Sat, 12 Jun 2004 19:17:51 +0200 (CEST) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with SMTP id 56FBE49D for ; Sat, 12 Jun 2004 19:17:51 +0200 (CEST) Date: Sat, 12 Jun 2004 19:17:44 +0200 From: Benjamin Lutz To: freebsd-questions@freebsd.org Message-Id: <20040612191744.67f25616.benlutz@datacomm.ch> X-Mailer: Sylpheed version 0.9.9-gtk2-20040229 (GTK+ 2.4.2; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Sat__12_Jun_2004_19_17_44_+0200_8IuYQoOllDBh/4+2" X-Virus-Scanned: by amavisd-new at maxlor.mine.nu Subject: Resource temporarily unavailable crash in vi X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jun 2004 17:18:06 -0000 --Signature=_Sat__12_Jun_2004_19_17_44_+0200_8IuYQoOllDBh/4+2 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Hello, I'm lately experiencing the "Resource temporarily unavailable" crash in vi a lot. I've had the same thing happen in other programs (eg, cvs, while it was waiting for input), so it's not something that's specific to vi. Someone even had it happen with cat: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-08/0497.html I went about investigating this occurance. I added an abort() to strerror() so I would get a coredump before the error message is printed. The results are a bit surprising: #0 0x2814406f in kill () from /lib/libc.so.5 #1 0x28138da8 in raise () from /lib/libc.so.5 #2 0x281ae493 in abort () from /lib/libc.so.5 #3 0x28193be3 in strerror () from /lib/libc.so.5 #4 0x08053e15 in free () #5 0x0804bcc0 in free () #6 0x0804b929 in free () #7 0x08050b85 in free () #8 0x0807e331 in free () #9 0x0807d12e in free () #10 0x0807cb8c in free () #11 0x08053307 in free () #12 0x0804b063 in free () #13 0x0804a3b9 in free () I then found these two postings that seem to point in the correct direction: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-08/0094.html http://monkey.org/openbsd/archive/misc/0310/msg01101.html This vi thing has happened most often while i working in KDE's Konsole. I'd open a new window, switch back to the old one, and vi would have crashed. It also happens when I'm starting vi in a Konsole. Now, I think the problem (or one of the programs that make it apparent) is Konsole. However, before filing a bug report, I'd like to get some more information. If you've ever encountered this bug, what were the circumstances? If you've researched it some, what did you find out? Greetings Benjamin Lutz --Signature=_Sat__12_Jun_2004_19_17_44_+0200_8IuYQoOllDBh/4+2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAyzq7gShs4qbRdeQRAhXDAJ45cll0kbrnMx++sziOLSVFv0d/JQCfbWgC Ydc0crcDEMveMvT9DQ/eMvI= =WAbg -----END PGP SIGNATURE----- --Signature=_Sat__12_Jun_2004_19_17_44_+0200_8IuYQoOllDBh/4+2--