On Tue, 30 Jul 2002, Oren Tirosh wrote: > I ran some tests with Julian Seward's amazing Valgrind memory debugger. > Python is remarkably clean. Much cleaner than any other program of > non-trivial size that I tested. I've been using Python with valgrind too, and with great success. I've caught several non-trivial problems in some of our extension modules, though only a few very picky things in the Python core. Valgrind has options to attached gdb to running processes when problems occur. Combining this with gdb patched to produce mixed C/Python tracebacks, and you get an awesome memory debugger. -Kevin -- Kevin Jacobs The OPAL Group - Enterprise Systems Architect Voice: (216) 986-0710 x 19 E-mail: jacobs@theopalgroup.com Fax: (216) 986-0714 WWW: http://www.theopalgroup.com
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