From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: allocate_string_data memory corruption Date: Thu, 19 Jan 2006 15:57:01 -0500 Message-ID: References: <87vewha2zl.fsf@stupidchicken.com> <87wtgxdr9p.fsf@stupidchicken.com> <873bjkha3d.fsf@pacem.orebokech.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1137709141 31080 80.91.229.2 (19 Jan 2006 22:19:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 Jan 2006 22:19:01 +0000 (UTC) Cc: Chong Yidong , Ken Raeburn , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 19 23:18:57 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 1Ezi7B-0003SK-D1 for ged-emacs-devel@m.gmane.org; Thu, 19 Jan 2006 23:18:46 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ezi92-00055W-R2 for ged-emacs-devel@m.gmane.org; Thu, 19 Jan 2006 17:20:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ezgsf-0006fJ-TD for emacs-devel@gnu.org; Thu, 19 Jan 2006 15:59:42 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ezgsd-0006dI-Nr for emacs-devel@gnu.org; Thu, 19 Jan 2006 15:59:40 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ezgsd-0006d1-4p for emacs-devel@gnu.org; Thu, 19 Jan 2006 15:59:39 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Ezgwi-000792-Oo for emacs-devel@gnu.org; Thu, 19 Jan 2006 16:03:53 -0500 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 2791F2CF75B; Thu, 19 Jan 2006 15:57:05 -0500 (EST) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id BCE4A4AC017; Thu, 19 Jan 2006 15:57:01 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id A93D7E6C1C; Thu, 19 Jan 2006 15:57:01 -0500 (EST) Original-To: Romain Francoise In-Reply-To: <873bjkha3d.fsf@pacem.orebokech.com> (Romain Francoise's message of "Thu, 19 Jan 2006 09:53:58 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.854, requis 5, autolearn=not spam, AWL 0.05, BAYES_00 -4.90) X-MailScanner-From: monnier@iro.umontreal.ca 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:49275 Archived-At: >> 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.) I still believe in the race-condition-with-signal-handler, because I'm absolutely sure there are bugs left in that area (which is why I came up with the SYNC_INPUT patch in the first place). Stefan