[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

2009-02-08 Thread Hirokazu Yamamoto
Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment: This seems to be duplicate of issue1856. Let me close this entry. -- resolution: - duplicate status: open - closed superseder: - shutdown (exit) can hang or segfault with daemon threads running

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

2009-02-07 Thread Corey Goldberg
Corey Goldberg cgoldb...@gmail.com added the comment: note: on Windows Vista it is not ery intermittant :) crashes every time the program is stopped. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5160

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

2009-02-06 Thread Hirokazu Yamamoto
Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment: Here is stack trace. PyEval_EvalFrameEx(_frame * 0x00a62060, int 83) line 2841 + 6 bytes fast_function(_object * 0x, _object * * * 0x00fbfa98, int 1, int 1, int 9870576) line 3946 call_function(_object * * * 0x00fbfa98, int

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

2009-02-05 Thread Corey Goldberg
New submission from Corey Goldberg cgoldb...@gmail.com: I can get the Python interpreter to core dump when running the following code: http://pastebin.com/f261f398f To reproduce: - run the above code and press ctrl-c to quit while it is running. It crashes (segfault) the interpreter every few

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

2009-02-05 Thread Corey Goldberg
Corey Goldberg cgoldb...@gmail.com added the comment: little more info: If you create a Queue in the main thread and pass this to each worker thread, it works fine. If you create the Queue inside the worker thread and then pass it to a new thread, it can crash. when it crashes, you get an