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: Mon, 11 Aug 2025 20:26:38 +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: Mon, 11 Aug 2025 13:20:05 -0400
> 
> Yes, sorry, I missed that there are two separate mechanisms.  I think
> set-process-thread should continue setting the thread member of the
> process object, but not the thread member of the fd_callback_info struct.

Why not?  set-process-thread can be called when the descriptors for
the process are already set up.  That's unlike make-process, which
indeed doesn't set the .thread member of the descriptors.

> Yes.  Let's just make set-process-thread stop setting the thread member
> of the fd_callback_info struct.

I don't agree it shouldn't see above.  What problems do you see as the
result of that?

Previous Next

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