GNU bug report logs - #33016
26.1; (make-process ...) doesn't signal an error, when executable given as absolute Windows path does not exist

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 33016 <at> debbugs.gnu.org, bauer.klaus.dieter <at> gmail.com
Subject: Re: bug#33016: 26.1;
 (make-process ...) doesn't signal an error, when executable given as
 absolute Windows path does not exist
Date: Fri, 12 Apr 2019 11:44:49 +0300

> From: Noam Postavsky <npostavs <at> gmail.com>
> Cc: 33016 <at> debbugs.gnu.org,  bauer.klaus.dieter <at> gmail.com
> Date: Thu, 11 Apr 2019 20:44:15 -0400
> 
> > OK.  That diff includes some unrelated stuff, though -- you didn't
> > mean to install it as is, right?
> 
> Ah, I left in the .gdbinit change completely by accident.  The other
> stuff is related, but wasn't cleaned up properly yet.  Here's a proper patch:

Thanks.

> +                    ;; On Windows, "nul.FOO" is the empty file for any
> +                    ;; FOO, in any directory.  So this passes Emacs'
> +                    ;; test for the file's existence, and ensures we
> +                    ;; hit an error in the w32 process spawn code.
> +                    (call-process "c:/nul.exe")

What happened to mentioning the null device in this comment?

> +                     (setq when-entered-debugger -1))))

This should be internal-when-entered-debugger, right?  And the same in
the other test.

Previous Next

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