>> Do you have an example bug where this patch helps in finding the precise >> location of a segfault? > > How is 'line 29 in g' not more precise than 'Segmentation fault'? I think Stefan is treating "precise location" as an absolute property, not a relative one. The precise location would be the very instruction causing the fault; this is something that a core dump provides, unless a signal handler interferes with that. In many crashes I fixed, the Python stack trace was irrelevant to understand the nature of the crash. Of course, there were also counter- examples where you'ld need the Python stack (or, rather, the entire interpreter trace) to understand how the crashing case can occur in the first place. Regards, Martin
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