A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-June/120385.html below:

[Python-Dev] What's the best way to debug python3 source code? (for this bug: http://bugs.python.org/issue15068)

[Python-Dev] What's the best way to debug python3 source code? (for this bug: http://bugs.python.org/issue15068) [Python-Dev] What's the best way to debug python3 source code? (for this bug: http://bugs.python.org/issue15068)"Martin v. Löwis" martin at v.loewis.de
Mon Jun 18 23:03:16 CEST 2012
> But i can't get any clue which file to look at.

I personally wouldn't use gdb but strace to establish what system calls
are being made, and decide whether these system calls are correct or
not. If you then think that some call is being made that shouldn't,
set a breakpoint on the syscall function, and see when it gets hit.

I'd also attach to a running Python interpreter instead of running
python from gdb, since the interaction between gdb's stdin
and python's stdin may be confusing.

Regards,
Martin

More information about the Python-Dev mailing list

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