This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients alfps, amaury.forgeotdarc, brian.curtin, ggenellina
Date 2010-03-09.13:22:52
SpamBayes Score 0.00015137134
Marked as misclassified No
Message-id <1268140975.69.0.170392112859.issue8036@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2010-03-09 13:22:55amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, ggenellina, brian.curtin, alfps
2010-03-09 13:22:55amaury.forgeotdarcsetmessageid: <1268140975.69.0.170392112859.issue8036@psf.upfronthosting.co.za>
2010-03-09 13:22:52amaury.forgeotdarclinkissue8036 messages
2010-03-09 13:22:52amaury.forgeotdarccreate