GNU bug report logs - #58956
mark_object, mark_objects(?) crash

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#58956: closed (mark_object, mark_objects(?) crash)
Date: Thu, 10 Nov 2022 10:15:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 10 Nov 2022 12:14:31 +0200
with message-id <83a64zru9k.fsf <at> gnu.org>
and subject line Re: bug#58956: mark_object, mark_objects(?) crash
has caused the debbugs.gnu.org bug report #58956,
regarding mark_object, mark_objects(?) crash
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
58956: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58956
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: bug-gnu-emacs <at> gnu.org
Subject: mark_object, mark_objects(?) crash
Date: Tue, 01 Nov 2022 18:33:38 -0700

[Message part 3 (text/plain, inline)]

Hello,

A Debian user has reported a crash with Emacs 28.  I'm attaching the
backtrace he provided.  We currently have the two recent trampoline fork
bomb patches from Andreas applied; I don't think any of our other
patches are relevant.

<https://bugs.debian.org/1017711>

-- 
Sean Whitton

[gdb.txt (text/plain, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 58956-done <at> debbugs.gnu.org, spwhitton <at> spwhitton.name, vincent <at> vinc17.net,
 1017711 <at> bugs.debian.org, akrl <at> sdf.org
Subject: Re: bug#58956: mark_object, mark_objects(?) crash
Date: Thu, 10 Nov 2022 12:14:31 +0200

> Date: Sat, 5 Nov 2022 13:54:54 -0700
> Cc: vincent <at> vinc17.net, spwhitton <at> spwhitton.name, 58956 <at> debbugs.gnu.org,
>  1017711 <at> bugs.debian.org
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> 
> On 2022-11-04 00:00, Eli Zaretskii wrote:
> > We need to establish what is the
> > source of SIGHUP in these cases.  "These cases" mean, AFAIU, the
> > situations where Emacs launched an async subprocess to do native
> > compilation (which is another Emacs process in a --batch session), and
> > the parent Emacs session is terminated by the user before the async
> > compilation runs to completion.  Would the child Emacs process get
> > SIGHUP in this scenario?
> 
> Hard for me to say. It's a messy area, with kernels (and Emacs itself) 
> sending SIGHUP on various whims.
> 
> Does the attached patch fix things? It builds on your commit 
> 190a6853708ab22072437f6ebd93beb3ec1a9ce6 dated 2020-12-04; I don't know 
> why that earlier patch was installed, but it would seem to apply to 
> SIGHUP and SIGTERM as well as it applies to SIGINT.

No further comments, so I've now installed this on the master branch,
and I'm marking this bug done.

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.