[issue33384] Build does not work with closed stdin on NetBSD

2019-10-24 Thread Leonardo Taccari
Leonardo Taccari added the comment: Hello Victor, I can confirm that I can no longer reproduce this problem with Python 3.7.5 on NetBSD and according a double-check to Python/pylifecycle.c:is_valid_fd() now fstat() is always used on NetBSD. Thanks for the update and for looking at it

[issue33384] Build does not work with closed stdin

2018-05-19 Thread Leonardo Taccari
Change by Leonardo Taccari : Added file: https://bugs.python.org/file47605/is_valid_fd.c ___ Python tracker <https://bugs.python.org/issue33384> ___ ___ Python-bugs-list m

[issue33384] Build does not work with closed stdin

2018-05-19 Thread Leonardo Taccari
Leonardo Taccari added the comment: After testing is_valid_fd() (from Python/pylifecycle.c) separately (an `is_valid_fd.c' file will be attached to ease reproduction) I think that also NetBSD is affected by bpo-30225. Using dup(2) (at is currently done in NetBSD): % cc -

[issue33384] Build does not work with closed stdin

2018-05-19 Thread Leonardo Taccari
Leonardo Taccari added the comment: And here the backtrace of the corresponding core (this is on NetBSD/amd64 8.99.15 with lang/python36 package of today pkgsrc-current): % gdb -core python3.6.core `which python3.6` Reading symbols from /usr/pkg/bin/python3.6...done. [New process 1

[issue33384] Build does not work with closed stdin

2018-05-19 Thread Leonardo Taccari
Leonardo Taccari added the comment: A simpler way to reproduce that (probably this problem is not limited to building but to sys module): (sleep 10; python3.6 -c 'import sys' >/tmp/log 2>&1) & exit And in `/tmp/log': Fatal Python error: Py_Initialize: