GNU bug report logs - #79201
30.1.90; set-process-thread can permanently break fd_callback_info slots

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Spencer Baugh <sbaugh <at> janestreet.com>
Cc: 79201 <at> debbugs.gnu.org, dmitry <at> gutov.dev, johnw <at> gnu.org, app-emacs-dev <at> janestreet.com
Subject: bug#79201: 30.1.90; set-process-thread can permanently break fd_callback_info slots
Date: Wed, 13 Aug 2025 19:57:41 +0300

> From: Spencer Baugh <sbaugh <at> janestreet.com>
> Cc: 79201 <at> debbugs.gnu.org,  dmitry <at> gutov.dev,  johnw <at> gnu.org,
>    app-emacs-dev <at> janestreet.com
> Date: Wed, 13 Aug 2025 12:46:39 -0400
> 
> > Could the above scenario be the reason for what you see?
> 
> No, because the non-nil waiting_thread is seen in make-process, for a
> process and file descriptor that is newly created.

Then I think the descriptors was closed without clearing the
.waiting_thread member.  So that goes back to what I suggested
up-thread: delete_read_fd and delete_write_fd should clear these
members.  They are called either after closing the descriptor or when
we stop reading/writing to them, so their .waiting_thread member is no
longer useful.

Previous Next

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