From owner-freebsd-questions@FreeBSD.ORG Sun Jun 13 17:50:44 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 C7AFF16A4CE for ; Sun, 13 Jun 2004 17:50:44 +0000 (GMT) Received: from adsl-68-76-19-75.dsl.klmzmi.ameritech.net (adsl-68-76-19-75.dsl.klmzmi.ameritech.net [68.76.19.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95FE943D1D for ; Sun, 13 Jun 2004 17:50:43 +0000 (GMT) (envelope-from luke@foolishgames.com) Received: from [192.168.2.49] (adsl-68-73-70-68.dsl.klmzmi.ameritech.net [68.73.70.68]) (authenticated bits=0)ESMTP id i5DHnjCj073537; Sun, 13 Jun 2004 13:49:47 -0400 (EDT) (envelope-from luke@foolishgames.com) In-Reply-To: <20040612191744.67f25616.benlutz@datacomm.ch> References: <20040612191744.67f25616.benlutz@datacomm.ch> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5548BC12-BD4E-11D8-BCB7-000A95EFF4CA@foolishgames.com> Content-Transfer-Encoding: 7bit From: Lucas Holt Date: Sun, 13 Jun 2004 11:28:34 -0400 To: Benjamin Lutz X-Mailer: Apple Mail (2.618) X-Virus-Scanned: clamd / ClamAV version 0.72, clamav-milter version 0.72 on adsl-68-76-19-75.dsl.klmzmi.ameritech.net X-Virus-Status: Clean cc: freebsd-questions@freebsd.org Subject: Re: 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: Sun, 13 Jun 2004 17:50:44 -0000 I've experienced this bug on several occasions. Each time I was using vi over a ssh session. X11 was not loaded on the system. I never did figure it out, and after a reinstall the problem did not occur often. I suspect it has something to do with virtual memory. On Jun 12, 2004, at 1:17 PM, Benjamin Lutz wrote: > 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 > Lucas Holt Luke@FoolishGames.com ________________________________________________________ FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) 'Mmm... forbidden donut' -- Homer Jay Simpson