From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.bugs Subject: bug#10322: 24.0.92; Crash on Mac OSX, Snow Leopard Date: Tue, 12 Feb 2013 21:37:55 -0500 Message-ID: <8wliatj5vg.fsf@fencepost.gnu.org> References: <39A88552-C999-4C6D-A4F0-4980D3336CFC@venalicium.dk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1360723123 6714 80.91.229.3 (13 Feb 2013 02:38:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 Feb 2013 02:38:43 +0000 (UTC) To: 10322-done@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Feb 13 03:39:04 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1U5SFP-0003cv-F8 for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Feb 2013 03:38:59 +0100 Original-Received: from localhost ([::1]:54451 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5SF6-0003eO-1O for geb-bug-gnu-emacs@m.gmane.org; Tue, 12 Feb 2013 21:38:40 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:55943) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5SF1-0003eG-7t for bug-gnu-emacs@gnu.org; Tue, 12 Feb 2013 21:38:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U5SF0-00045r-6G for bug-gnu-emacs@gnu.org; Tue, 12 Feb 2013 21:38:35 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:47533) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5SF0-00045m-2f for bug-gnu-emacs@gnu.org; Tue, 12 Feb 2013 21:38:34 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1U5SFS-0002oP-Ka for bug-gnu-emacs@gnu.org; Tue, 12 Feb 2013 21:39:02 -0500 Resent-From: Glenn Morris Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Feb 2013 02:39:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 10322 X-GNU-PR-Package: emacs,ns X-GNU-PR-Keywords: Mail-Followup-To: 10322@debbugs.gnu.org, rgm@gnu.org, colding@venalicium.dk Original-Received: via spool by 10322-done@debbugs.gnu.org id=D10322.136072310710733 (code D ref 10322); Wed, 13 Feb 2013 02:39:02 +0000 Original-Received: (at 10322-done) by debbugs.gnu.org; 13 Feb 2013 02:38:27 +0000 Original-Received: from localhost ([127.0.0.1]:52996 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U5SEs-0002n4-ST for submit@debbugs.gnu.org; Tue, 12 Feb 2013 21:38:27 -0500 Original-Received: from fencepost.gnu.org ([208.118.235.10]:55802) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U5SEq-0002mv-Rf for 10322-done@debbugs.gnu.org; Tue, 12 Feb 2013 21:38:25 -0500 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1U5SEN-0006eG-Dw; Tue, 12 Feb 2013 21:37:55 -0500 X-Spook: Rumsfeld security keyhole Etacs Croatian nitrate Abbas X-Ran: o}H X-Hue: black X-Attribution: GM In-Reply-To: (Jules Colding's message of "Tue, 20 Dec 2011 23:30:30 +0100") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:71135 Archived-At: Jules Colding wrote: >> tries to get the name of a symbol. On the other hand, the message it >> tries to print is "Error during redisplay: %S" so somthing went bad >> before that. It could be a threading issue that leads to some memory >> corruption. > > Possibly, I can't reproduce it so some obscure threading issues seem > likely. Closing, for now at least then.