New submission from Hirokazu Yamamoto <ocean-c...@m2.ccsnet.ne.jp>: I noticed test_close_open_print_buffered(test_file) sometimes crashes on release26-maint branch. This is most problamatic part in my python2.6 test survey on VC6 + Win2K.
Here is stacktrace. _write_lk(int 6, const void * 0x00b49240, unsigned int 11) line 155 + 3 bytes _write(int 6, const void * 0x00b49240, unsigned int 11) line 79 + 17 bytes _flush(_iobuf * 0x102618e8) line 162 + 23 bytes _fclose_lk(_iobuf * 0x102618e8) line 130 + 9 bytes fclose(_iobuf * 0x102618e8) line 67 + 9 bytes close_the_file(PyFileObject * 0x00a9e6b8) line 370 + 7 bytes file_close(PyFileObject * 0x00a9e6b8) line 570 + 9 bytes call_function(_object * * * 0x00fdf350, int 11134648) line 3734 + 204 bytes PyEval_EvalFrameEx(_frame * 0x00b33d50, int 131) line 2414 (snip) Python crashes when MSVCRT touches internal buffer of file object via flush() in close(). I think this is multi-threading bug related to internal buffer of file object. I'll post more. ---------- components: Interpreter Core messages: 110652 nosy: ocean-city priority: normal severity: normal stage: needs patch status: open title: test_close_open_print_buffered(test_file) sometimes crashes type: crash versions: Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9295> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
