[issue12209] Minor edits to faulthandler doc

2014-03-25 Thread Éric Araujo
Éric Araujo added the comment: Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue12209] Minor edits to faulthandler doc

2014-03-25 Thread STINNER Victor
STINNER Victor added the comment: Sorry for the delay. I applied your patch. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue12209] Minor edits to faulthandler doc

2014-03-25 Thread Roundup Robot
Roundup Robot added the comment: New changeset a97dcdee35f9 by Victor Stinner in branch '3.4': Issue #12209: Minor edits to faulthandler doc. Patch written by Éric Araujo. http://hg.python.org/cpython/rev/a97dcdee35f9 New changeset 6f80ca0012ae by Victor Stinner in branch 'default': (Merge 3.4)

[issue12209] Minor edits to faulthandler doc

2011-05-30 Thread Éric Araujo
Éric Araujo added the comment: 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? -- ___ Python tracker

[issue12209] Minor edits to faulthandler doc

2011-05-30 Thread STINNER Victor
STINNER Victor added the comment: > dumping the traceback on CPython crashes? 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(). --

[issue12209] Minor edits to faulthandler doc

2011-05-30 Thread Éric Araujo
Éric Araujo added the comment: > faulthandler prints the Python trace, not the C trace, so I prefer to > call it a "traceback" than "stack trace". Okay. What do you think about this synopsis then: dumping the traceback on CPython crashes? -- ___ Py

[issue12209] Minor edits to faulthandler doc

2011-05-29 Thread STINNER Victor
STINNER Victor added the comment: 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

[issue12209] Minor edits to faulthandler doc

2011-05-29 Thread Éric Araujo
New submission from Éric Araujo : 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”