From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Andrus Newsgroups: gmane.emacs.devel Subject: Re: Investigating crash (Bug#11395) on Mac OS Date: Fri, 4 May 2012 10:07:57 +0200 Message-ID: <56808EDA-49E8-4FAA-81EF-0A2B1577F141@gmail.com> References: <87r4v04qxi.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1336118901 18346 80.91.229.3 (4 May 2012 08:08:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 4 May 2012 08:08:21 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 04 10:08:20 2012 Return-path: Envelope-to: ged-emacs-devel@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 1SQDYq-0007HD-6C for ged-emacs-devel@m.gmane.org; Fri, 04 May 2012 10:08:20 +0200 Original-Received: from localhost ([::1]:52728 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQDYp-00040t-ET for ged-emacs-devel@m.gmane.org; Fri, 04 May 2012 04:08:19 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:58610) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQDYk-00040o-1D for emacs-devel@gnu.org; Fri, 04 May 2012 04:08:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SQDYi-0001L9-6n for emacs-devel@gnu.org; Fri, 04 May 2012 04:08:13 -0400 Original-Received: from mail-bk0-f41.google.com ([209.85.214.41]:39753) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQDYa-0001GG-7S; Fri, 04 May 2012 04:08:04 -0400 Original-Received: by bkcjm19 with SMTP id jm19so2521211bkc.0 for ; Fri, 04 May 2012 01:08:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=a79tV9nKoz9RPU4n/3Mydd38d1O62SzhMX/XQcGuaGk=; b=iOEwMK4ycaDRD/p2JbdyRjBP/ICvRtyCLXQHn08mn5T7idsniUCqClsVLc85LYV79T MoC+LqpWZelERb38qNUnPlVmXCH8AxGRMtsQBxSTTrzEEMEwK4URtlwXx8/6u1k/BjMF 4rt5WCZj5Knus18Im2s85aJuX2sx8tVVMOURuBCV9lI2hodLKwT2xuBJLfvKNr95g/lR ggD6SQRb5sHZD2Z0nx64UNY9WlmewIJXxccvblnGvqPdRv0BZeNMldUKz6sU4oXYc5Ep yMMcmtDeQhJGRRxJpmPRQdbdndbr1vLOSdK0dcOdSMg3drH85OxEqW1DIoBTNnFce0yo Iz8A== Original-Received: by 10.204.156.22 with SMTP id u22mr1706290bkw.22.1336118880668; Fri, 04 May 2012 01:08:00 -0700 (PDT) Original-Received: from [10.0.2.16] (catv-80-99-177-93.catv.broadband.hu. [80.99.177.93]) by mx.google.com with ESMTPS id h18sm15131520bkh.8.2012.05.04.01.07.58 (version=SSLv3 cipher=OTHER); Fri, 04 May 2012 01:07:59 -0700 (PDT) In-Reply-To: <87r4v04qxi.fsf@gnu.org> X-Mailer: Apple Mail (2.1084) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.214.41 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:150250 Archived-At: On May 4, 2012, at 4:32 AM, Chong Yidong wrote: > Could someone who is running on Mac OS please help investigate the = crash > reported at >=20 > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D11395 >=20 > ? It's claimed to be reproducible, but I can't get it to crash on my > end (x86_64-unknown-linux-gnu), so maybe some part of the Nextstep = code > is not GC-safe. >=20 > Thanks. I was getting this quite regularly (about every 15 minutes) a week ago = (from bzr head), but after I got done traveling (Tuesday) I updated and = I haven't experienced it since. I assumed someone had fixed it so I = didn't bother reporting it. In the past several years it has been very = stable updating from bzr head every so often. So at least for me it's = been very version dependent. When I debugged it once it was stuck in a loop with = internal_condition_case returning 0 (instead of Qnil) or something like = that. I also remember one time when the window information got = corrupted in some way so that point-min wasn't a marker. The result was = that I couldn't do anything including closing the window because it = would error. So it seems it's probably (random) memory corruption, but you probably = knew that. Why it's fixed now for me, I don't know. If you would like = I could try and bisect to see what changed. Hopefully it's not dependent = on the phase of the moon. :-) Is there anything else I could do to try = and figure it out? IIRC running it under valgrind, which would be my = first instinct, isn't supported. -Ivan=