raise ValueError for empty `path` in os.spawnv[e]

[alfps]

BPO	8036
Nosy	@loewis, @terryjreedy, @pfmoore, @amauryfa, @tjguk, @ezio-melotti, @briancurtin, @zware, @serhiy-storchaka, @eryksun, @zooba
Files	issue8036_0.patch issue_8036_1.patch: args checking + tests

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2010-03-01.21:12:27.159>
labels = ['type-bug', '3.8', '3.9', '3.10', 'library', 'OS-windows']
title = 'raise ValueError for empty `path` in os.spawnv[e]'
updated_at = <Date 2021-03-08.19:50:50.885>
user = 'https://bugs.python.org/alfps'

bugs.python.org fields:

activity = <Date 2021-03-08.19:50:50.885>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Windows']
creation = <Date 2010-03-01.21:12:27.159>
creator = 'alfps'
dependencies = []
files = ['21080', '23529']
hgrepos = []
issue_num = 8036
keywords = ['patch']
message_count = 20.0
messages = ['100272', '100281', '100699', '100718', '100720', '100721', '127123', '127124', '130563', '146327', '146329', '146369', '146370', '146453', '321356', '321357', '321358', '321398', '321405', '387874']
nosy_count = 17.0
nosy_names = ['loewis', 'terry.reedy', 'paul.moore', 'exarkun', 'amaury.forgeotdarc', 'ggenellina', 'dstanek', 'schmir', 'tim.golden', 'ezio.melotti', 'brian.curtin', 'alfps', 'nvetoshkin', 'zach.ware', 'serhiy.storchaka', 'eryksun', 'steve.dower']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue8036'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

[alfps]

In Windows XP, using CPython 3.1.1:

python -c "import os; os.spawnl( os.P_WAIT, 'blah' )"

Crashes the interpreter and Windows pops up the "tell us about it" box.

Python 2.6 is however happy and just reports invalid arg.

[briancurtin]

Confirmed on trunk, release31-maint, and py3k on Windows. OS X returns 127 in that case.

[ggenellina]

In case it matters, 3.0.1 does NOT crash.

[amauryfa]

2.6 and 3.0.1 used to disable the Microsoft CRT argument error handler: they return EINVAL, but newer versions don't, and should check their arguments before calling _spawnv.

FWIW, the checks are::
pathname != NULL
*pathname != '\0'
argv != NULL
*argv != NULL
**argv != '\0'
The first and third checks are guaranteed by the implementation, but the other three should be done in posix_spawnv().
And the other calls to the various nt.spawn* functions probably suffer the same problem.

[exarkun]

Why is the Microsoft CRT argument error handler no longer disabled?

[amauryfa]

Because this is a global setting for the whole process. This was discussed with bpo-4804.

[dstanek]

Should this just be resolved as a "won't fix"?

[amauryfa]

No, the issue can be fixed by better checking the arguments.

[nvetoshkin]

Attached first attempt to close this issue. Are there enough checks? It passes:
os.spawnl(os.P_WAIT, '')
os.spawnl(os.P_WAIT, 'path')
os.spawnl(os.P_WAIT, 'path', '')

[terryjreedy]

This came up on python-list with
os.spawnl (os.P_NOWAIT, r"c:\windows\notepad.exe")
Tim Golden confirmed crash with Win7 on 2.7.?
I did same with 3.2.2 in both interpreter and from IDLE (IDLE hangs and then restarts after closing the 'pythonw has stopped' error message box).
Above apparently works in XP, at least with Py2.2.

[vstinner]

@nvetoshkin: Can you please also write tests (in Lib/test/test_os.py) for your patch?

[nvetoshkin]

against py3k branch?