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 josh.r
Recipients execve, josh.r
Date 2018-11-06.17:07:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1541524069.14.0.788709270274.issue35180@psf.upfronthosting.co.za>
In-reply-to
Content
The TypeError on Py3 would be because functions taking c_char_p need bytes-like objects, not str, on Python 3. '%s' % directory is pointless when directory is a str; instead you need to encode it to a bytes-like object, e.g. opendir(os.fsencode(directory)) (os.fsencode is Python 3 specific; plain str works fine on Py 2).

Your segfault isn't occurring when you load dirfd, it occurs when you call it on the result of opendir, when opendir returned NULL on failure (due to the non-existent directory you call it with). You didn't check the return value, and end up doing flagrantly illegal things with it.

In neither case is this a bug in Python; ctypes lets you do evil things that break the rules, and if you break the rules the wrong way, segfaults are to be expected. Fix your argument types (for Py3), check your return values (for Py2).
History
Date User Action Args
2018-11-06 17:07:49josh.rsetrecipients: + josh.r, execve
2018-11-06 17:07:49josh.rsetmessageid: <1541524069.14.0.788709270274.issue35180@psf.upfronthosting.co.za>
2018-11-06 17:07:49josh.rlinkissue35180 messages
2018-11-06 17:07:49josh.rcreate