From owner-freebsd-current@FreeBSD.ORG  Sun Apr 18 08:31:32 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3D04A16A4E3
	for <current@freebsd.org>; Sun, 18 Apr 2004 08:31:32 -0700 (PDT)
Received: from geri.cc.fer.hr (geri.cc.fer.hr [161.53.72.107])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5A05943D2D
	for <current@freebsd.org>; Sun, 18 Apr 2004 08:31:31 -0700 (PDT)
	(envelope-from ivoras@fer.hr)
Received: from fer.hr (geri.cc.fer.hr [161.53.72.107])
	by geri.cc.fer.hr (8.12.9p2/8.12.8) with ESMTP id i3IFV91m093764
	for <current@freebsd.org>; Sun, 18 Apr 2004 17:31:10 +0200 (CEST)
	(envelope-from ivoras@fer.hr)
Message-ID: <40829F4F.6050004@fer.hr>
Date: Sun, 18 Apr 2004 17:31:27 +0200
From: Ivan Voras <ivoras@fer.hr>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: current@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: siege and libpthread
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Apr 2004 15:31:32 -0000

There are problems (segfault) running siege (web benchmark program) on a 
recent FreeBSD 5.2-current (a few days ago). When I switch it to libc_r 
via libmap.conf, everything works ok. Since the software is ported to a 
large number of platforms and works ok, it's probably a libpthread bug :)

Siege uses threading to make simultaneous HTTP requests. I tried with a 
recent release (2.59) and beta (2.60) version if siege, with same behaviour.

This does not happend with small number of threads (2-3), but if I 
specify a larger number (usually 8+), it crashes in the middle of work.