New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor edits to faulthandler doc #56418
Comments
I made some grammar fixes in faulthandler.rst and tweaked the example to better show what the module does. I’d like to fix the synopsis too: “dump the Python traceback” is not very clear to me. It is the traceback or the stack trace? Why is it called “the” traceback? Something like “dumping the stack trace on CPython crashes” would be better IMO. |
What do you call a "stack trace"? I use this term in the C language, especially when using the "where" command of gdb. In Python, the stack trace is called a "traceback". Anyway, faulthandler prints the Python trace, not the C trace, so I prefer to call it a "traceback" than "stack trace". faulthandler.dump_traceback() output is similar to:
faulthandler doesn't print the line from the script, only the function name, file name and line number; and the first line is different. |
|
faulthandler is no more specific to crashes: you can dump the tracebacks while Python is running using a signal or an explicit call to faulthandler.dump_traceback(). |
Okay, I understand now that the traceback always exists, not only during exceptions. The module gives control over the display of that traceback. Am I right? |
New changeset a97dcdee35f9 by Victor Stinner in branch '3.4': New changeset 6f80ca0012ae by Victor Stinner in branch 'default': |
Sorry for the delay. I applied your patch. |
Thanks! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: