From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HrFVz-0003BY-HW for qemu-devel@nongnu.org; Thu, 24 May 2007 11:46:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HrFVx-00038X-PN for qemu-devel@nongnu.org; Thu, 24 May 2007 11:46:11 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HrFVx-00038J-DP for qemu-devel@nongnu.org; Thu, 24 May 2007 11:46:09 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HrFVw-0007ge-MT for qemu-devel@nongnu.org; Thu, 24 May 2007 11:46:09 -0400 From: Paul Brook Subject: Re: [Qemu-devel] qemu-user mmap not thread-safe? Date: Thu, 24 May 2007 16:45:57 +0100 References: <4655A880.2000801@suse.de> In-Reply-To: <4655A880.2000801@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705241645.58693.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Alexander Graf On Thursday 24 May 2007, Alexander Graf wrote: > Hi, > > while playing around with TLS on i386 i came across this problem which > occurs even when no TLS is used at all. If two threads just malloc() > memory all the time I get a segmentation fault after a short time. Might > this be a serious bug? qemu is not even vaguely threadsafe. Paul