On 6/18/2012 12:43 AM, gmspro wrote:
What's the best way to debug python3 source code?
...
The pydev list is for development *of* future python releases. For
questions about development *with* current releases, please ask on
python-list or other user oriented forums.
--
Terry Jan Reedy
What's the best way to debug python3 source code?
To fix a bug i need to debug source code(C files).
I use gdb to debug.
If the bug is presumably in C, then using gdb works fine for me.
But how can i get the exact file/point to fix the bug?
As usual: set breakpoints and watch points. In
@martin,
I'm working on this bug, http://bugs.python.org/issue15068
I tried this with gdb
(gdb)run
from sys import stdin
str=sys.stdin.read()
blabla
blabla
blabla
CTRL+D
CTRL+D
CTRL+C
(gdb)backtrace
0xb7f08348 in ___newselect_nocancel () at ../sysdeps/unix/syscall-template.S:82
82
On 6/18/2012 7:10 AM, gmspro wrote:
I'm working on this bug, http://bugs.python.org/issue15068
Oh. From your first message, I thought you were asking about a personal
bug. I will mention that real names are customary on this list. (Unless
you have a good professional reason otherwise.) They
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
Hi,
What's the best way to debug python3 source code?
To fix a bug i need to debug source code(C files).
I use gdb to debug.
But how can i get the exact file/point to fix the bug?
How can i know quickly where the bug is?
How can i run python from gdb and giving input there how can i test and
