GNU bug report logs - #14297
24.3.50; emacs subprocesses don't exit on "exit"

Previous Next

Full log

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

From: Vitalie Spinu <spinuvit <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Paul Eggert <eggert <at> cs.ucla.edu>,
 14297 <at> debbugs.gnu.org
Subject: Re: bug#14297: 24.3.50; emacs subprocesses don't exit on "exit"
Date: Sat, 26 Dec 2015 01:19:22 +0100

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

Yes. It has been gone for me for long.

On 26 December 2015 at 00:45, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:

> Paul Eggert <eggert <at> cs.ucla.edu> writes:
>
> > On second thought, please forget my patch.  get_child_status will abort
> > anyway, if the bug that I hypothesized occurs, so my patch isn't needed.
> >
> > On 05/13/13 10:41, Eli Zaretskii wrote:
> >
> >> How about this alternative idea: write a replacement waitpid, which
> >> will check if it is called by someone other than our main thread, and
> >> with its first argument negative, and then produce a backtrace or some
> >> message to stderr?  Would that work to trap calls to waitpid from GTK?
> >
> > That could well work, yes, and it might be worth trying if we see
> > the right symptoms.  But since get_child_status is not aborting I
> > don't think we're seeing the right symptoms.
>
> The problem here seemed to be with Gtk under Kubuntu.  Is this still a
> problem, or has it gone away during the last two years?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[Message part 2 (text/html, inline)]

Previous Next

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