[issue7111] core dump when stderr is moved

2009-10-24 Thread Matteo Bertini
Matteo Bertini added the comment: sorry, title restored! -- title: stdout closed -> core dump when stderr is moved ___ Python tracker ___

[issue7111] core dump when stderr is moved

2009-10-24 Thread Matteo Bertini
Changes by Matteo Bertini : -- nosy: +naufraghi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7111] core dump when stderr is moved

2009-10-14 Thread Peter Eisentraut
Peter Eisentraut added the comment: For what it's worth, the code in question is used here (using "import distutils" instead of "pass"): http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/config/python.m4?rev=1.15;content-type=text%2Fx-cvsweb-markup This is obviously a completely gratuitous varian

[issue7111] core dump when stderr is moved

2009-10-14 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: > 3.1 exits silently. Did you use "print"? pythonw.exe 3.1 sets sys.stdout to None. if you use sys.stdout.write, you get an exception. But print() silently does nothing if the file is None. -- nosy: +amaury.forgeotdarc ___

[issue7111] core dump when stderr is moved

2009-10-13 Thread Daniel Stutzbach
Daniel Stutzbach added the comment: Is it even possible to portably test the validity of a file descriptor without trying to write/read it? When I first saw this bug, my gut feeling was "well, don't do that then!" However, I then recalled that Windows GUI applications have no stdin, stdout, or

[issue7111] core dump when stderr is moved

2009-10-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Please note that normally an error message is output, but of course it doesn't display since stderr is invalid :-) It's clearer if you close stdout instead: $ ./python -c 'pass' >&- Fatal Python error: Py_Initialize: can't initialize sys standard streams OSErr

[issue7111] core dump when stderr is moved

2009-10-13 Thread Daniel Stutzbach
Daniel Stutzbach added the comment: After some searching around with Google, "2>&-" means "close file descriptor 2" (i.e., standard error). -- nosy: +stutzbach ___ Python tracker ___

[issue7111] core dump when stderr is moved

2009-10-12 Thread Benjamin Peterson
Benjamin Peterson added the comment: The problem is the check_fd in _fileio.c checks fstat of 2, which returns EBADFD. I'm not sure what about this redirection makes it a bad file descriptor, though.. -- nosy: +benjamin.peterson ___ Python tracker <

[issue7111] core dump when stderr is moved

2009-10-12 Thread Matthias Klose
Changes by Matthias Klose : -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue7111] core dump when stderr is moved

2009-10-12 Thread Peter Eisentraut
New submission from Peter Eisentraut : bash$ python3.1 -c 'pass' 2>&- Aborted (core dumped) (I verified, the core dump belongs to python.) If you remove the redirection thingy at the end, it works. Not sure why I ever wrote that code, but it has been working since forever up to python3.0. ---