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: Wed, 9 May 2012 21:23:57 +0200 Message-ID: <1F4745AE-7674-4807-970D-19C702774A51@gmail.com> References: <87r4v04qxi.fsf@gnu.org> <56808EDA-49E8-4FAA-81EF-0A2B1577F141@gmail.com> <87havwxmbs.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 1336591456 15134 80.91.229.3 (9 May 2012 19:24:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 9 May 2012 19:24:16 +0000 (UTC) To: Emacs Dev Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 09 21:24:15 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 1SSCUc-0007d2-11 for ged-emacs-devel@m.gmane.org; Wed, 09 May 2012 21:24:10 +0200 Original-Received: from localhost ([::1]:34232 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SSCUb-0003c0-CD for ged-emacs-devel@m.gmane.org; Wed, 09 May 2012 15:24:09 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:59654) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SSCUW-0003bQ-LS for emacs-devel@gnu.org; Wed, 09 May 2012 15:24:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SSCUT-0000Pa-KC for emacs-devel@gnu.org; Wed, 09 May 2012 15:24:04 -0400 Original-Received: from mail-bk0-f41.google.com ([209.85.214.41]:37862) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SSCUT-0000N7-AL for emacs-devel@gnu.org; Wed, 09 May 2012 15:24:01 -0400 Original-Received: by bkcjm19 with SMTP id jm19so737707bkc.0 for ; Wed, 09 May 2012 12:23:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=KlDvkY9PJmXZ0fk/VvpezxBelEK36pmw7H0BpQEnPx0=; b=BN/Wc5LZBiM/yaEUGsh1UVxA1eGp558Vgd0gdwFrUnqU6fWlNb8ujH6H4RoWJ8nfsE wtg94uHzQ5qu0wCe3X1nID1sOQPrCSWD9YlEovWvX6S6wMUmEe2sJslxr5EuvdjdV8jo dxS4gEb/tOzGILsPmiV7PiQcvJGJLaEpVym7953guAyOo+PBObfyww8rKU0WC4fHo8JL xU/FhqyQaLmcGtie35L4CabaJEuHXnKNV8TXG8jAlIiMyNBqAKF6Qu1aiIGCVA6Vu4bl h0Tuaj5qqbIf+2FiM9ihdLA2NIlst79JT3UWWPduUIO81xzqbz9BX6bBNjvi7WvFq8Kj nPOA== Original-Received: by 10.205.128.8 with SMTP id hc8mr531373bkc.17.1336591439252; Wed, 09 May 2012 12:23:59 -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 u8sm7214710bks.0.2012.05.09.12.23.57 (version=SSLv3 cipher=OTHER); Wed, 09 May 2012 12:23:58 -0700 (PDT) In-Reply-To: <87havwxmbs.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:150410 Archived-At: On May 4, 2012, at 12:38 PM, Chong Yidong wrote: > Ivan Andrus writes: >=20 >> 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. >=20 > If this is right, there may have been a fix committed to trunk but > missing from the release branch (since Bug#11395 was reported for the > 24.0.96 pretest). >=20 > If you can, please try bisecting. That would help tremendously. The > (so far incomplete) recipe posted by Richard Stanton in the bug page = for > Bug#11395 may help if you can reproduce it. My attempts at bisecting were an utter failure. First I had problems = building after using bzr bisect so I decided to bisect "manually". I = was able to easily reproduce the problem with some revisions e.g. 108034 = by repeatedly exporting an org file to pdf (only required 3-5 exports). = I was unable (after 10-15 exports) to reproduce the problem with other = revisions e.g. 108049. I had to leave it though, and now that I come = back to it I can't reproduce the problem with revision 108034. So = there's something weird going on. FWIW I was trying to bisect "backwards" by finding the revision where it = was fixed for me. There were far fewer commits that way since I hadn't = previously updated for about a month. >> IIRC running it under valgrind, which would be my first instinct, >> isn't supported. >=20 > Running `valgrind ./temacs -l loadup' works for me (apart from the = usual > cloud of false positives due to GC). But maybe it doesn't work on Mac > OS, I dunno. That's good to know. But `valgrind ./emacs` wouldn't work I assume? = Anyway, I'll try it later if I can reproduce the error. -Ivan=