From owner-freebsd-ports-bugs@FreeBSD.ORG  Tue Jan 17 21:12:26 2006
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
X-Original-To: freebsd-ports-bugs@freebsd.org
Delivered-To: freebsd-ports-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8629A16A41F
	for <freebsd-ports-bugs@freebsd.org>;
	Tue, 17 Jan 2006 21:12:26 +0000 (GMT)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net
	[67.168.241.176])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 24B4A43D49
	for <freebsd-ports-bugs@freebsd.org>;
	Tue, 17 Jan 2006 21:12:26 +0000 (GMT)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com (uucp@localhost)
	by schitzo.solgatos.com (8.11.6/8.11.6) with UUCP id k0HLCHI04300;
	Tue, 17 Jan 2006 13:12:17 -0800
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id VAA17483; Tue, 17 Jan 2006 21:08:40 GMT
Message-Id: <200601172108.VAA17483@sopwith.solgatos.com>
To: alex@semenyaka.ru, freebsd-ports-bugs@freebsd.org
Date: Tue, 17 Jan 2006 13:08:40 +0000
From: Dieter <freebsd@sopwith.solgatos.com>
Cc: 
Subject: Re: ports/91923: links dumps core while visiting some web-pages
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: freebsd@sopwith.solgatos.com
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
	<mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
	<mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2006 21:12:26 -0000

Links doesn't dump core for http://www.sendspace.com/file/q3xrzz
if javascript is turned off.

Perhaps a clue to where the bug is?
Perhaps a workaround until a fix is found?