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

Previous Next

Full log

Message #50 received at 58956 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 58956 <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: Sun, 06 Nov 2022 21:58:26 +0200

> Date: Sun, 6 Nov 2022 11:44:43 -0800
> Cc: akrl <at> sdf.org, 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-06 11:32, Eli Zaretskii wrote:
> > My question was whether in this scenario, since the parent Emacs
> > exits, the child Emacs can get SIGHUP, simply because its parent
> > exited and the read end of the PTY no longer exists.
> 
> Yes, my sense from the few experiments I tried, is that it's a plausible 
> scenario, though I never observed it actually happening for Emacs doing 
> a subprocess compile.

OK, thanks.  So I hope your suggested patch will solve this issue.

Previous Next

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