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

[Noam Postavsky]

On Fri, 12 Apr 2019 at 04:45, Eli Zaretskii <eliz@gnu.org> wrote:

> > +                    ;; 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?

Yeah, I forgot to change this comment (though I don't think
specifically naming the null device is needed).

> > +                     (setq when-entered-debugger -1))))
>
> This should be internal-when-entered-debugger, right?  And the same in
> the other test.

Oops, right, that's what I get for rushing things. I think got
everything this time (include replacing RMS' question in eval.c).

v5-0001-Let-debugger-handle-process-spawn-errors-on-w32-B.patch
Description: Binary data