"Tim Peters" <tim.one@home.com> wrote: > Unsurprisingly, it's importing test_b2.py at this point. > So this is enough to reproduce the problem: ... > Best guess is that I need a debug build to fail, because > in the normal build > it's still referencing free()d memory anyway, but the > normal MS malloc/free > don't overwrite free()d memory with trash (so the > problem isn't noticed). > No guess as to why -O is needed. This sounds like there's a difference in when someting gets DECREFed differently when the optimizations are performed; perhaps that code hasn't kept up with the pace of change? I'm not familiar enough with that code to be able to check it quickly with any level of confidence, however. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4