[issue29712] --enable-optimizations does not work with --enable-shared
Stefan Ring added the comment: I was having the same problem, and I just found out what it was: Because of -Wl,-rpath=..., this path gets baked into the binary, and LD_LIBRARY_PATH is ignored. So if you have a previous build lying around there, it will mess up the build. -- nosy: +Ringding ___ Python tracker <https://bugs.python.org/issue29712> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17094] sys._current_frames() reports too many/wrong stack frames
Stefan Ring added the comment: When I originally worked on this, I noticed that _PyThread_CurrentFrames also iterates over all interpreters. Because I have no experience with or use for multiple interpreters, I intentionally left it out of my patch, but shouldn't it be taken into account for a real patch? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17094 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17094] sys._current_frames() reports too many/wrong stack frames
Stefan Ring added the comment: (Regarding your test) I have also noticed in the past that joining threads after a fork has caused hangs occasionally, although that might have resulted from the messed up _current_frames. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17094 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17094] sys._current_frames() reports too many/wrong stack frames
New submission from Stefan Ring: After a fork, the list of thread states contains all the threads from before. It is especially unfortunate that, at least for me, it usually happens that threads created in the forked process reuse the same thread ids, and sys._current_frames will then return wrong stack frames for existing threads because the old entries occur towards the tail of the linked list and overwrite the earlier, correct ones, in _PyThread_CurrentFrames. The attached patch is certainly not the most complete solution, but it solves my problem. With Python 2.7.3 I get: Exception in thread Thread-6: Traceback (most recent call last): File /usr/lib64/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib64/python2.7/threading.py, line 504, in run self.__target(*self.__args, **self.__kwargs) File test-fork-frames.py, line 24, in do_verify assert frame_from_sys is real_frame AssertionError With my patch applied, it passes silently. I can reproduce this on CentOS 6.3 x86_64 as well as Fedora 18 x86_64. -- components: Interpreter Core files: current-frames-cleanup.patch keywords: patch messages: 181045 nosy: Ringding priority: normal severity: normal status: open title: sys._current_frames() reports too many/wrong stack frames type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file28924/current-frames-cleanup.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17094 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17094] sys._current_frames() reports too many/wrong stack frames
Changes by Stefan Ring stefan...@gmail.com: Added file: http://bugs.python.org/file28925/test-fork-frames.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17094 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0
Changes by Stefan Ring stefan...@gmail.com: -- nosy: +Ringding ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8271 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty
Changes by Stefan Ring stefan...@gmail.com: -- nosy: +Ringding ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5322 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5912] import deadlocks when using fork
Changes by Stefan Ring stefan...@gmail.com: -- nosy: +Ringding ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5912 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1540386] SocketServer.ForkingMixIn.collect_children() waits on pid 0
Stefan Ring stefan...@gmail.com added the comment: Jeffrey, this very commit broke it. See also issue 5814. The same happened for me last week. What makes it especially bad is that even once enough children terminate, the SocketServer won't be able to handle any more connections; it just throws this Exception again and again and closes new connections immediately. -- nosy: +Ringding ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1540386 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
