GNU bug report logs - #29454
wait_reading_process_output duplication

Previous Next

Package: emacs;

Reported by: charles <at> aurox.ch (Charles A. Roelli)

Date: Sun, 26 Nov 2017 09:45:02 UTC

Severity: normal

Done: charles <at> aurox.ch (Charles A. Roelli)

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29454 in the body.
You can then email your comments to 29454 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#29454; Package emacs. (Sun, 26 Nov 2017 09:45:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to charles <at> aurox.ch (Charles A. Roelli):
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 26 Nov 2017 09:45:02 GMT) Full text and rfc822 format available.

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

From: charles <at> aurox.ch (Charles A. Roelli)
To: bug-gnu-emacs <at> gnu.org
Subject: wait_reading_process_output duplication
Date: Sun, 26 Nov 2017 10:45:53 +0100
Looks like these two blocks are duplicated in
wait_reading_process_output in process.c:

5628 #ifdef WINDOWSNT
5629 	      /* FIXME: Is this special case still needed?  */
5630 	      /* Note that we cannot distinguish between no input
5631 		 available now and a closed pipe.
5632 		 With luck, a closed pipe will be accompanied by
5633 		 subprocess termination and SIGCHLD.  */
5634 	      else if (nread == 0 && !NETCONN_P (proc) && !SERIALCONN_P (proc)
5635 		       && !PIPECONN_P (proc))
5636 		;
5637 #endif

5664 	      /* If we can detect process termination, don't consider the
5665 		 process gone just because its pipe is closed.  */
5666 	      else if (nread == 0 && !NETCONN_P (proc) && !SERIALCONN_P (proc)
5667 		       && !PIPECONN_P (proc))
5668 		;

Can the first be deleted?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#29454; Package emacs. (Sun, 26 Nov 2017 15:55:01 GMT) Full text and rfc822 format available.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: charles <at> aurox.ch (Charles A. Roelli)
Cc: 29454 <at> debbugs.gnu.org
Subject: Re: bug#29454: wait_reading_process_output duplication
Date: Sun, 26 Nov 2017 17:54:00 +0200
> Date: Sun, 26 Nov 2017 10:45:53 +0100
> From: charles <at> aurox.ch (Charles A. Roelli)
> 
> Looks like these two blocks are duplicated in
> wait_reading_process_output in process.c:
> 
> 5628 #ifdef WINDOWSNT
> 5629 	      /* FIXME: Is this special case still needed?  */
> 5630 	      /* Note that we cannot distinguish between no input
> 5631 		 available now and a closed pipe.
> 5632 		 With luck, a closed pipe will be accompanied by
> 5633 		 subprocess termination and SIGCHLD.  */
> 5634 	      else if (nread == 0 && !NETCONN_P (proc) && !SERIALCONN_P (proc)
> 5635 		       && !PIPECONN_P (proc))
> 5636 		;
> 5637 #endif
> 
> 5664 	      /* If we can detect process termination, don't consider the
> 5665 		 process gone just because its pipe is closed.  */
> 5666 	      else if (nread == 0 && !NETCONN_P (proc) && !SERIALCONN_P (proc)
> 5667 		       && !PIPECONN_P (proc))
> 5668 		;
> 
> Can the first be deleted?

Yes.  (The second was originally conditioned on SIGCHLD, which is why
it was separate.)

Thanks.




Reply sent to charles <at> aurox.ch (Charles A. Roelli):
You have taken responsibility. (Sun, 26 Nov 2017 19:44:01 GMT) Full text and rfc822 format available.

Notification sent to charles <at> aurox.ch (Charles A. Roelli):
bug acknowledged by developer. (Sun, 26 Nov 2017 19:44:01 GMT) Full text and rfc822 format available.

Message #13 received at 29454-done <at> debbugs.gnu.org (full text, mbox):

From: charles <at> aurox.ch (Charles A. Roelli)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 29454-done <at> debbugs.gnu.org
Subject: Re: bug#29454: wait_reading_process_output duplication
Date: Sun, 26 Nov 2017 20:44:27 +0100
> Date: Sun, 26 Nov 2017 17:54:00 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> CC: 29454 <at> debbugs.gnu.org
> Reply-to: Eli Zaretskii <eliz <at> gnu.org>
> 
> > Date: Sun, 26 Nov 2017 10:45:53 +0100
> > From: charles <at> aurox.ch (Charles A. Roelli)
> > 
> > Looks like these two blocks are duplicated in
> > wait_reading_process_output in process.c:
> > 
> > 5628 #ifdef WINDOWSNT
> > 5629 	      /* FIXME: Is this special case still needed?  */
> > 5630 	      /* Note that we cannot distinguish between no input
> > 5631 		 available now and a closed pipe.
> > 5632 		 With luck, a closed pipe will be accompanied by
> > 5633 		 subprocess termination and SIGCHLD.  */
> > 5634 	      else if (nread == 0 && !NETCONN_P (proc) && !SERIALCONN_P (proc)
> > 5635 		       && !PIPECONN_P (proc))
> > 5636 		;
> > 5637 #endif
> > 
> > 5664 	      /* If we can detect process termination, don't consider the
> > 5665 		 process gone just because its pipe is closed.  */
> > 5666 	      else if (nread == 0 && !NETCONN_P (proc) && !SERIALCONN_P (proc)
> > 5667 		       && !PIPECONN_P (proc))
> > 5668 		;
> > 
> > Can the first be deleted?
> 
> Yes.  (The second was originally conditioned on SIGCHLD, which is why
> it was separate.)
> 
> Thanks.

Thanks, it's pushed to master.

  commit 6ec5d497b6623e612ca6936ac848234725d4fc61
  Date:   Sun Nov 26 20:18:54 2017 +0100

  * src/process.c (wait_reading_process_output): Deduplicate check.

  (Bug#29454)




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Mon, 25 Dec 2017 12:24:06 GMT) Full text and rfc822 format available.

This bug report was last modified 7 years and 239 days ago.

Previous Next


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