From owner-freebsd-threads@FreeBSD.ORG  Wed Nov 19 13:27:55 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5A32616A4D0
	for <threads@freebsd.org>; Wed, 19 Nov 2003 13:27:55 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3283243F3F
	for <threads@freebsd.org>; Wed, 19 Nov 2003 13:27:54 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id hAJLRp1G027408;
	Wed, 19 Nov 2003 16:27:51 -0500 (EST)
Date: Wed, 19 Nov 2003 16:27:51 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Marcel Moolenaar <marcel@xcllnt.net>
In-Reply-To: <20031117014620.GB61716@dhcp01.pn.xcllnt.net>
Message-ID: <Pine.GSO.4.10.10311191627050.15552-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: David Xu <davidxu@viatech.com.cn>
cc: threads@freebsd.org
Subject: Re: KSE/ia64 broken
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2003 21:27:55 -0000

On Sun, 16 Nov 2003, Marcel Moolenaar wrote:

> On Mon, Nov 17, 2003 at 09:35:21AM +0800, David Xu wrote:
> > >
> > The returned memory block from malloc() is being used by unknown code, I 
> > don't know
> > why it occurs, but if you waste a memory block by applying the following 
> > patch for
> > thr_alloc(), then things work:
> 
> The memory block is clobbered by a ucontext_t. This may be the result
> of the kernel doing the upcall (though indirectly I would suspect).

Any more on this.  I haven't been able to find anything
on our end.

-- 
Dan Eischen