From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Romain Francoise Newsgroups: gmane.emacs.devel Subject: Re: allocate_string_data memory corruption Date: Thu, 19 Jan 2006 09:53:58 +0100 Organization: orebokech dot com Message-ID: <873bjkha3d.fsf@pacem.orebokech.com> References: <87vewha2zl.fsf@stupidchicken.com> <87wtgxdr9p.fsf@stupidchicken.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1137703934 9720 80.91.229.2 (19 Jan 2006 20:52:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 Jan 2006 20:52:14 +0000 (UTC) Cc: Ken Raeburn , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 19 21:52:10 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Ezgl7-0007CH-Dt for ged-emacs-devel@m.gmane.org; Thu, 19 Jan 2006 21:51:54 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EzgnZ-0004RV-GU for ged-emacs-devel@m.gmane.org; Thu, 19 Jan 2006 15:54:25 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EzVaV-00015P-1X for emacs-devel@gnu.org; Thu, 19 Jan 2006 03:56:11 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EzVaS-000152-OO for emacs-devel@gnu.org; Thu, 19 Jan 2006 03:56:10 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EzVaS-00014s-45 for emacs-devel@gnu.org; Thu, 19 Jan 2006 03:56:08 -0500 Original-Received: from [82.67.41.165] (helo=yeast.orebokech.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EzVeS-0000Yz-9y for emacs-devel@gnu.org; Thu, 19 Jan 2006 04:00:16 -0500 Original-Received: from pacem.orebokech.com (pacem.orebokech.com [192.168.1.3]) by yeast.orebokech.com (Postfix) with ESMTP id F3C9C12CF9; Thu, 19 Jan 2006 09:53:33 +0100 (CET) Original-Received: by pacem.orebokech.com (Postfix, from userid 1000) id 0195352391; Thu, 19 Jan 2006 09:53:58 +0100 (CET) Original-To: Chong Yidong X-Face: }9mYu,e_@+e!`Z-P5kVXa3\_b:hdJ"B)ww[&=b<2=awG:GOIM (Chong Yidong's message of "Wed, 18 Jan 2006 18:56:34 -0500") X-Mailman-Approved-At: Thu, 19 Jan 2006 14:27:26 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:49271 Archived-At: Chong Yidong writes: > He has a certain Emacs Lisp setup that he can use to crash Emacs > reproducibly, when hyperthreading is turned on. Without > hyperthreading, he has gotten one or two strange bus errors, but these > seem to be difficult to reproduce, and we're not sure if they are > real. Hmm... bus errors are quite uncommon on i386, are you 100% sure that we're looking at a software problem here? It's possible that this user's machine has faulty RAM chips that cause random memory corruption, and that HyperThreading worsens the problem because it increases memory pressure. Can the problem be reproduced on several machines? If not, could the user run memtest86+ on that one machine? If this is a problem specific to HT, it strikes me as suspicious that we got only *one* report given the number of people who use the CVS version of Emacs. (For the record, my main work machine has HyperThreading and Emacs hasn't crashed there for many months now.) -- Romain Francoise | The sea! the sea! the open it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the | ever free! --Bryan W. Procter