Python Debugging Tips: Difference between revisions
No edit summary |
AutoSpider (talk | contribs) (Rename category "LanguageBindings::PySide" -> "PySide") |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:PySide]] | |||
This Wiki page lists some useful tips for analyzing unexpected behaviors in Python programs. | This Wiki page lists some useful tips for analyzing unexpected behaviors in Python programs. | ||
| Line 7: | Line 9: | ||
== Using Python trace module == | == Using Python trace module == | ||
If your program is crashing and no information is being shown about what happened (as usually is the case with a segfault), then the Python module '''trace''' can be useful to point which line of the program is causing the crash or at least the line where the program stopped. Just add | If your program is crashing and no information is being shown about what happened (as usually is the case with a segfault), then the Python module '''trace''' can be useful to point which line of the program is causing the crash or at least the line where the program stopped. Just add "-m trace —trace" parameters to the Python executable and every line being executed will be printed on the screen. Supposing your program is called 'script.py', one way to use '''trace''' is shown below: | ||
<code> | <code> | ||
$ python -m trace —trace script.py | |||
</code> | |||
Keep in mind that this will make your program run slower, as the standard output will show everything being executed at the time. For more information about the '''trace''' module, you can consult its official documentation | Keep in mind that this will make your program run slower, as the standard output will show everything being executed at the time. For more information about the '''trace''' module, you can consult its official documentation [http://docs.python.org/library/trace.html here.] | ||
Latest revision as of 03:31, 5 June 2016
This Wiki page lists some useful tips for analyzing unexpected behaviors in Python programs.
Using Python trace module
If your program is crashing and no information is being shown about what happened (as usually is the case with a segfault), then the Python module trace can be useful to point which line of the program is causing the crash or at least the line where the program stopped. Just add "-m trace —trace" parameters to the Python executable and every line being executed will be printed on the screen. Supposing your program is called 'script.py', one way to use trace is shown below:
$ python -m trace —trace script.py
Keep in mind that this will make your program run slower, as the standard output will show everything being executed at the time. For more information about the trace module, you can consult its official documentation here.