From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Umar Ahmad via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#50284: 28.0.50; Emacs crashes occasionally on macOS BigSur Date: Thu, 30 Sep 2021 16:53:27 +0530 Message-ID: References: <83lf4hu8ne.fsf@gnu.org> <874ka39xqu.fsf@gnus.org> <83fstmh16r.fsf@gnu.org> Reply-To: Umar Ahmad Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000009e4fb405cd34ade8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3853"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 50284@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 30 13:24:11 2021 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 1mVuAb-0000rV-QP for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 30 Sep 2021 13:24:10 +0200 Original-Received: from localhost ([::1]:46286 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mVuAa-0002Zd-SB for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 30 Sep 2021 07:24:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58424) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVuAU-0002ZN-13 for bug-gnu-emacs@gnu.org; Thu, 30 Sep 2021 07:24:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40047) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mVuAT-000200-Q8 for bug-gnu-emacs@gnu.org; Thu, 30 Sep 2021 07:24:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mVuAT-0002P6-Me for bug-gnu-emacs@gnu.org; Thu, 30 Sep 2021 07:24:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Umar Ahmad Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 30 Sep 2021 11:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50284 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 50284-submit@debbugs.gnu.org id=B50284.16330010359223 (code B ref 50284); Thu, 30 Sep 2021 11:24:01 +0000 Original-Received: (at 50284) by debbugs.gnu.org; 30 Sep 2021 11:23:55 +0000 Original-Received: from localhost ([127.0.0.1]:51593 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mVuAN-0002Oh-39 for submit@debbugs.gnu.org; Thu, 30 Sep 2021 07:23:55 -0400 Original-Received: from sonic314-19.consmr.mail.sg3.yahoo.com ([106.10.240.143]:39612) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mVuAK-0002OT-6U for 50284@debbugs.gnu.org; Thu, 30 Sep 2021 07:23:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.in; s=s2048; t=1633001024; bh=9+91VIinNe/SXerNEDiatXQASBAgeLj97OSZN1V37Ic=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From:Subject:Reply-To; b=qJJj7f7pUmOSnZfKDuCwgIVExChKhr5VtjR5L6RLrvhiYbjRaxAbhNETaUUM7ZcyXDO/4LYnh0pYBnYAV7JbXbEEHZx73Fo2qPBvhJKSN1JoBE7iwUENjjs2YOskq2rbAH4/9DcNgZbdfdlMg9LhKygkV0/kJKjIXh4eMAuR137bpguGg+irN6DH5F2DYTskcASfksG3CE4PpBX/dPOOHJw+0xt7EEmijDSnz2p4Jeeb1JLdFe/SwaADaX/PCyglL4bgBzm6PiKmjaah5vtbAnXMz+SweNpImw3avuA/WcMMJQT1L8YIhrpmsAi103hJZ4m4Klw9SZmyBUFvivOU5w== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1633001024; bh=hmnlctM3kuTqwBnCsMHZuaAFEoMehIBVinL4Ssbl0kL=; h=X-Sonic-MF:From:Date:Subject:To:From:Subject; b=thG3ar7tBb2aRLvM+qh2n/bwKrqxCQ2N7S1zUjtZe10z4LvbQ6aZk691bbd/+cdhpo0OMgLv+JnDG8GoTl1U7f+/Ih0U/0EpOXG00Sne12V3E7HCukD2flOwEFbU6y1MBcA51zPOZKY6Mvs3AEdaaN1w2+I4VLQGa9qEKd5DZfypZdbDWfVi5RtKelujJZdSakcda5Bv4KpS0sDdm/u/8aw33jMzZDedVyaMthYyUV8DOJXC47nTvvJNzzbxtGhEneAzG50B13qdynmpbrc9xI6mDWlviUwdnUUVDJ5HcDhPHWDdBxI11jUorOC51tWzga3AxpRiVz3AxhCHnIwnXQ== X-YMail-OSG: 6C_nWC4VM1l6GGYFtkjJYBBN0hbIbbAgx9XNmhfavDr.gEDaYR14NXIbOnCP6QJ jvtd_C7O97M29J_Eg92.73uqFoqTL22of9FdqN6pVWj1gy0HSsvUwt2SwxDU7BWHUXRR0YOuNo7z b9LT67.D_UEoaJ7N_ICVq4gzYf73I9YqmRUQllOAFAuVSZCaXXDACT78rAfanOiycbZslJ5ILnW_ H4.UEMNShpo.ddeM4GsktvqURU2AK53tpsl85d1n8rGwK.Hoy1s8WpN70aQLrNYCsqK7WcTFJwPR A0jr1G9jVDWw2h3ZCD_GYwEH1HNE5U1fEUeRHI_9UhS0XBgNTFMuphE4Dw4IpjjIbNUb5kE87XFX DoDADxn3i3Z_ZYTihIX3EuWCj0WJh_lVl4LUSoSae5ZNlt1NzGABe6UrhOROyVs1Vgs7ccro49ZW _1TgvgKqqu9RcX832J5CW1EaHqYvgwaLtLvP57wyPSuNLucbtYg2J5gncgSAjs5quqORefsjtrKu 2n1snj9AOqDQE.hgIHB1LMK265KwsqpIC08CrxReZpykkOw1t_Kas9kPwasZzvniOfHRFjBHSjxt HkDN.Y_EEMxECJ3gq4JPwaOgjdiCdFHGNFTdh3BazXJ5hNszO4ykUqoQzEEMpJ0UKeAivNzGYySw lAvHWFp4AHQWcn65XOV_.ux74f1vdHx1PmpEUHoQKlHw_FP4B4QNCqpn81cfwnb5px0vschcPnri d_Br._rhskZmdSZh3eV.bbuWq5z70l62aSXQyLP4xF446bkFs_sgLipZ7tW.b.X4xSGmoW3EDn8h ivfMijOCLXRXSXN95IhXrbLxwsWfOpoSclUugGrQ62 X-Sonic-MF: Original-Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.sg3.yahoo.com with HTTP; Thu, 30 Sep 2021 11:23:44 +0000 Original-Received: by kubenode518.mail-prod1.omega.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 092634347f4a8eafda8fd05b191f4776; Thu, 30 Sep 2021 11:23:40 +0000 (UTC) Original-Received: by mail-io1-f48.google.com with SMTP id b10so7024432ioq.9 for <50284@debbugs.gnu.org>; Thu, 30 Sep 2021 04:23:40 -0700 (PDT) X-Gm-Message-State: AOAM531nVssWMQxdtRVyrg0glCuAnsaY698MtahJzeW42J/nfIzHMyLG di13XogVt7Hs6+GfVh/IxAycmmGiXrZafk2zXXI= X-Google-Smtp-Source: ABdhPJw1jkQ7Xq8Ipry014woVglFf44TkDusM+EqRDTfVpvrkaFdttc+JEGZGAenckpgfd0TrGLgV3S+2wIynLxhlJQ= X-Received: by 2002:a05:6602:2193:: with SMTP id b19mr3476619iob.27.1633001018378; Thu, 30 Sep 2021 04:23:38 -0700 (PDT) In-Reply-To: <83fstmh16r.fsf@gnu.org> X-Gmail-Original-Message-ID: X-Mailer: WebService/1.1.19076 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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:215961 Archived-At: --0000000000009e4fb405cd34ade8 Content-Type: text/plain; charset="UTF-8" Hello Eli, Thank you for your answers. Yes the bug can be closed. On Thu, Sep 30, 2021 at 2:47 PM Eli Zaretskii wrote: > > From: Umar Ahmad > > Date: Thu, 30 Sep 2021 02:14:06 +0530 > > Cc: Eli Zaretskii , 50284@debbugs.gnu.org > > > > Anyway, I think you're right to point out that it was some lisp code > that was > > the culprit here. I've been running emacs continuously for the last 20 > days > > without a crash. This closely matches the time I upgraded all the > packages, so I > > think it's fair to assume that some package upgrade solved it. > > > > I was under the assumption that any lisp code crashing emacs would be a > bug in > > Emacs, but I guess we can keep this closed, considering that I can't > replicate > > it now. > > A Lisp bug shouldn't in general crash Emacs, but infinite recursion in > Lisp is an exception: it is not always possible to recover from that, > although Emacs does try. > > > > We need to know where in regex-emacs.c is the place shown in the last > line > > above. Can you try establishing that? > > > > I've no idea on how to establish that considering my rudimentary > knowledge of > > C. Do you mean, running emacs with GDB enabled and adding breakpoints to > figure > > this out? > > It is enough to run under GDB and produce a backtrace when the crash > happens. > > > > This indicates that you are using s.el, which makes tracking this bug > harder. > > > > Oh! I see. Didn't know this could make things harder. > > It is harder because to try anything we would need to install s.el. > > > > So I think we need to see the full Lisp backtrace when this happens, > or at > > least the Lisp code which runs. > > > > Got it. I only knew of `toggle-debug-on-error`, at the time of reporting > this > > bug, that would give me a trace if there were some errors in elisp but I > didn't > > know, how I could've managed to get the lisp trace when emacs crashes. I > just > > discovered the /etc/DEBUG file, after going through your mail, and it > seems the > > way to do this is again through GDB and running xbacktrace. Is this the > correct > > understanding or is there some other way to achieve this? > > Yes. In fact, if you start GDB from the src directory with Emacs > sources, the "backtrace" command will automatically run "xbacktrace" > as well, because we arrange for that in src/.gdbinit. > > So I guess we should close this bug for now? > -- Regards, Umar Ahmad --0000000000009e4fb405cd34ade8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Eli,
Thank you for your answers. Yes = the bug can be closed.

On Thu, Sep 30, 2021 at 2:47 PM Eli Zaretsk= ii <eliz@gnu.org> wrote:
> From: Umar Ahmad &l= t;ahmad.umar20= 08@yahoo.in>
> Date: Thu, 30 Sep 2021 02:14:06 +0530
> Cc: Eli Zaretskii <eliz@gnu.org>, 50284@debbugs.gnu.org
>
> Anyway, I think you're right to point out that it was some lisp co= de that was
> the culprit here. I've been running emacs continuously for the las= t 20 days
> without a crash. This closely matches the time I upgraded all the pack= ages, so I
> think it's fair to assume that some package upgrade solved it.
>
> I was under the assumption that any lisp code crashing emacs would be = a bug in
> Emacs, but I guess we can keep this closed, considering that I can'= ;t replicate
> it now.

A Lisp bug shouldn't in general crash Emacs, but infinite recursion in<= br> Lisp is an exception: it is not always possible to recover from that,
although Emacs does try.

> > We need to know where in regex-emacs.c is the place shown in the = last line
> above.=C2=A0 Can you try establishing that?
>
> I've no idea on how to establish that considering my rudimentary k= nowledge of
> C. Do you mean, running emacs with GDB enabled and adding breakpoints = to figure
> this out?

It is enough to run under GDB and produce a backtrace when the crash
happens.

> > This indicates that you are using s.el, which makes tracking this= bug harder.
>
> Oh! I see. Didn't know this could make things harder.

It is harder because to try anything we would need to install s.el.

> > So I think we need to see the full Lisp backtrace when this happe= ns, or at
> least the Lisp code which runs.
>
> Got it. I only knew of `toggle-debug-on-error`, at the time of reporti= ng this
> bug, that would give me a trace if there were some errors in elisp but= I didn't
> know, how I could've managed to get the lisp trace when emacs cras= hes. I just
> discovered the /etc/DEBUG file, after going through your mail, and it = seems the
> way to do this is again through GDB and running xbacktrace. Is this th= e correct
> understanding or is there some other way to achieve this?

Yes.=C2=A0 In fact, if you start GDB from the src directory with Emacs
sources, the "backtrace" command will automatically run "xba= cktrace"
as well, because we arrange for that in src/.gdbinit.

So I guess we should close this bug for now?


--
Regards,
Umar Ahmad
--0000000000009e4fb405cd34ade8--