X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 03 Dec 2007 15:50:23 -0800 From: David Rothenberger Subject: Re: 1.5.25-3: Problem with pinfo In-reply-to: <31DDB7BE4BF41D4888D41709C476B6570929A6E0@NIHCESMLBX5.nih.gov> To: cygwin AT cygwin DOT com Message-id: <4754963F.8060407@acm.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <31DDB7BE4BF41D4888D41709C476B6570929A6E0 AT NIHCESMLBX5 DOT nih DOT gov> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 12/3/2007 3:27 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote: > David Rothenberger wrote on Monday, December 03, 2007 12:36 PM: >> I'm having a problem with pinfo under 1.5.25-3. The problem is not >> there with 1.5.24-2. >> >> - From a Windows cmd shell, I start bash with "bash -li". Then, I run >> "pinfo rxvt". pinfo just dies with the message "Hangup". I see the >> following in the cmd shell window: >> >> 22 [sig] pinfo 6788 C:\cygwin\bin\pinfo.exe: *** fatal error - >> called with threadlist_ix -1 > > See if this fixes things for you > /> sh -c /etc/postinstall/update-info-dir.sh.done It does not, but thanks for the suggestion. > As a diagnostic or workaround, you might also see if regular info works. info works fine, as does pinfo with cygwin 1.5.24. -- David Rothenberger ---- daveroth AT acm DOT org Spence's Admonition: Never stow away on a kamikaze plane. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/