Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 21 Jun 2005 14:15:39 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: lynx getting segv when following a link with right arrow key
Message-ID: <20050621121539.GH2814@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20050621011321 DOT GA3060 AT efn DOT org> <20050621031427 DOT GC9195 AT trixie DOT casa DOT cgf DOT cx> <20050621032418 DOT GA1060 AT efn DOT org> <20050621040034 DOT GA20129 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050621040034.GA20129@trixie.casa.cgf.cx>
User-Agent: Mutt/1.4.2i

On Jun 21 00:00, Christopher Faylor wrote:
> On Mon, Jun 20, 2005 at 08:24:19PM -0700, Yitzchak Scott-Thoennes wrote:
> >On Mon, Jun 20, 2005 at 11:14:27PM -0400, Christopher Faylor wrote:
> >>On Mon, Jun 20, 2005 at 06:13:22PM -0700, Yitzchak Scott-Thoennes
> >>wrote:
> >>>On the 20050615 snapshot (and maybe other releases, haven't used lynx
> >>>in a while) lynx is repeatably segfaulting when I use the right arrow
> >>>key to follow a link.
> >>
> >>Can't duplicate this.  Sorry.  Do you have a specific site which
> >>demonstrates the problem?
> >
> >Sorry for the lack of details; I was a bit rushed earlier.
> >
> >Any site, AFAICT.  Just starting lynx with no parameters goes to
> >http://lynx.browser.org, with the http://lynx.isc.org/release/ "Lynx
> >2.8.3" link highlighted.  Pressing the right arrow key gets:
> 
> I managed to duplicate it ten seconds after sending my above message, of
> course.
> 
> If the problem is really what it appears to be, it's rather incredible.
> It seems like the IsBadWritePtr function in thread.cc is tripping 
> lynx's SIGSEGV handler.  I didn't think that was possible.  It sort
> of defeats the whole purpose of IsBadWritePtr.  I have to think about
> this one...

While there might be a problem with IsBadWritePtr at one point, it's
not the problem in Lynx.  Unfortunately Lynx uses some Windowism in
the Cygwin version, which in turn crashes when trying to retrieve thread
local storage from another thread.

I changed the Lynx configuration so that POSIX calls are used and
uploaded a new version.


Thanks for the report,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/