From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.bugs Subject: bug#39962: 27.0.90; Crash in Emacs 27.0.90 Date: Wed, 18 Mar 2020 14:08:19 +0000 Message-ID: References: <24162.58107.725366.668639@cochabamba.vanoostrum.org> <83y2s48yn7.fsf@gnu.org> <83zhck6obg.fsf@gnu.org> <83r1xv73ze.fsf@gnu.org> <83imj5bdct.fsf@gnu.org> <83zhcff131.fsf@gnu.org> <2b2fc990-2917-7970-d88b-7708dbaa48be@cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="93745"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Robert Pluim , Paul Eggert , 39962@debbugs.gnu.org To: Pieter van Oostrum Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Mar 18 15:10:12 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jEZOe-000OJQ-7I for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 18 Mar 2020 15:10:12 +0100 Original-Received: from localhost ([::1]:51156 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jEZOd-00049X-9X for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 18 Mar 2020 10:10:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47849) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jEZOV-00047k-Hl for bug-gnu-emacs@gnu.org; Wed, 18 Mar 2020 10:10:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jEZOU-0000lc-95 for bug-gnu-emacs@gnu.org; Wed, 18 Mar 2020 10:10:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:35005) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jEZOU-0000ky-39 for bug-gnu-emacs@gnu.org; Wed, 18 Mar 2020 10:10:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jEZOT-00030D-Sg for bug-gnu-emacs@gnu.org; Wed, 18 Mar 2020 10:10:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 18 Mar 2020 14:10:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39962 X-GNU-PR-Package: emacs Original-Received: via spool by 39962-submit@debbugs.gnu.org id=B39962.158454054511470 (code B ref 39962); Wed, 18 Mar 2020 14:10:01 +0000 Original-Received: (at 39962) by debbugs.gnu.org; 18 Mar 2020 14:09:05 +0000 Original-Received: from localhost ([127.0.0.1]:40978 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jEZNZ-0002yr-9J for submit@debbugs.gnu.org; Wed, 18 Mar 2020 10:09:05 -0400 Original-Received: from mail-ot1-f41.google.com ([209.85.210.41]:33419) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jEZNW-0002yG-NV for 39962@debbugs.gnu.org; Wed, 18 Mar 2020 10:09:03 -0400 Original-Received: by mail-ot1-f41.google.com with SMTP id x26so8583545otk.0 for <39962@debbugs.gnu.org>; Wed, 18 Mar 2020 07:09:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=PIQ116V/i4tpe/vT+kIHm/SZbROuNL1E54USOEORVdQ=; b=CENswSIeRC9eVcbJJ3JG8GCTXspuL52pFGHkc3QqOtgo/uMM5jHByfC5dFuL+hyAFa 4vjYBGIKB2pvmyPi43UEk50TDEbwn2v5naDFluo4MOFrdNNwu+Bap/QbSUSJ/b03Vf6K BFGTuTPbnzetavH8LrgbQvtNuRwsCc+Iiijusrg2AeVpOmVFYFxobD2hHJJgmFt77kds yIVHr/ahj6LGbx8a33cZagahrB3/jGnrXT9hLrwa966OSRzoBZYsq0iSAqcCd11R68dL DKOXfOi5FR9aPYtX1x/XziUF7FxDb8En3UjcnBM7NEr6Fwuwz3xLgNYLOnugVJKsmPBk fCog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=PIQ116V/i4tpe/vT+kIHm/SZbROuNL1E54USOEORVdQ=; b=G3T4N3xz5CVBrNZ6AGrph4omwKA7uPiwPTE2uN9S97I42vvMQVQq0rZ1C2pIlXqzgP 1ISiy8wAumJZAH43OpKp/ZTacbclP9PdEX2vaRij5xkXA7GTTrRhtnVWHeSzpDrFg+Oq rT1lqhTRdbv1aKj8DBBdA5+ilwp7EqUQuBGmwynfd7mDWaFQLV4/pxbMzm7ZD3CESJFT WkdsrICAnHmYIl+rVlRV8GrOc8PQqSSOA3z7OUuLeSDlAMB0ruDELHCsplkvkl1J6Du/ bb8Ckla/mKICsqdECJqpO2e8Iaga0N1/xNqHVavGUh8UpFIiofhhKiK7gRjNWC4IhtG2 yUiQ== X-Gm-Message-State: ANhLgQ2ZCFKJzEKQ0nnGh1etN+RSlban8uwolM7bbsxU+hY+DMRAqUDB EUVixCMW9XJg9AFPr6DMHVyfWBs9G42QplTdxxM= X-Google-Smtp-Source: ADFU+vuyh2VmRSbMXWisMUUu7vNS9sLaYba28gluKn465sjouLa9xzjvcY78AarhFLo0Chee5hmMdxG2K+mGxatKkEg= X-Received: by 2002:a05:6830:19ee:: with SMTP id t14mr4197218ott.287.1584540536892; Wed, 18 Mar 2020 07:08:56 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:177493 Archived-At: On Wed, Mar 18, 2020 at 11:38 AM Pieter van Oostrum wrote: > Robert Pluim writes: > >>>>>> On Wed, 18 Mar 2020 06:17:01 +0000, Pip Cet sai= d: > > > > Pip> On Tue, Mar 17, 2020 at 8:59 PM Paul Eggert wrote: > > >> Although I haven't been following this in detail, I'd like to su= ggest trying a > > >> GDB watchpoint to find the bug. Watchpoints have been invaluable= to me when I > > >> debug garbage-collector and other memory management issues. > > > > Pip> They are! Unfortunately, they require a predictable address at= which > > Pip> the corruption happens, and we don't appear to have that. > > > > You have a known address if you use rr and run in reverse. Indeed, which makes debugging on GNU/Linux a lot easier. Unfortunately, I strongly suspect this problem is specific to macOS, and I'm not aware of a reverse debugger for that OS. > I have a procedure to generate a crash, but it isn't very predictable. I = think that is because there are timers running and asynchronous processes. = I get a different crash each time I run it. I think it's because of user interaction and the events it generates... > The crash generation involves opening two large mailboxes with VM (it cou= ld be that one would also work). I then manipulate them both, re-sorting th= em in a different order, saving, switching between the two, sorting back to= my preferred order, saving and closing. I have saved this procedure in a k= eyboard macro, giving it a name. I copied the definition to another Emacs s= ession. To recreate the crash, I copy the definition to the new Emacs sessi= on in the *scratch* buffer, and I can then invoke it with C-x C-e. For the = latest crash, I entered C-x C-e some 40 times, and went to bed. After I awo= ke, Emacs had not crashed yet. So I entered a few more C-x C-e, and then it= crashed immediately. But it was different than the previous one. So, actua= lly, I think it will be very difficult to find proper watch points. Is it possible this is somehow related to mouse/keyboard interaction? That's my prime suspect, anyway; I still think that macOS runs code asynchronously upon receiving external events in ways that aren't kosher, particularly if they happen during GC. If I'm right, it should be possible to trigger the bug by creating a reasonably large session, running (garbage-collect) in an infinite loop, and interacting with the mouse and keyboard while that is happening. Or running your keyboard macro in a similar loop, of course.