I'm currently able to pretty reliably produce a core file using Zope 2.5.0 and Python 2.1.3 on a box based on RedHat 6.2. The core is produced due to a segfault, from in select.so. I can look at the backtrace, and I've done some preliminary inspection of the active code object, the call out to select.so, etc. I haven't learned much as a consequence of that, unfortunately: the args passed to the C function don't appear to be a valid python object (can't access the type object), though the function seems okay; and I don't appear to have a filename for my code object (just /). My backtraces appear to vary in quality (not sure why) -- sometimes I get all the symbols I expect, sometimes I get no symbols at all. The best traceback I have at the moment (though I I'm writing now in the hopes that some of the regulars here have some standard recipes for extracting useful information from the backtraces that I might get something approaching a reconstruction of the python code that's being executed, and the arguments that are being supplied. If nobody's got any hints, that's fine, I'm still working on it -- but if you do, I'd appreciate it. Thanks, --G. -- Geoff Gerrietts <geoff at gerrietts net> "A man can't be too careful in the choice of his enemies." --Oscar Wilde
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