Ryan Gonzalez added the comment:

What if you run:



On August 15, 2015 7:32:37 PM CDT, Cyd Haselton <rep...@bugs.python.org> wrote:
>Cyd Haselton added the comment:
>I thought porting gdb would be the difficult part of getting debug
>info. I was so wrong.
>Here is what I have so far, after lengthy consultation of the gdb
>manual.  Bear with me...it's basically a copy & paste of gdb session
>(gdb) run
>Starting program: /bld/pyt/cpython-android/python
>setpgrp failed in child: No such process
>warning: Unable to find dynamic linker breakpoint function.
>GDB will be unable to debug shared library initializers
>and track explicitly loaded dynamic code.
>Program received signal SIGILL, Illegal instruction.
>0xb6a63cc8 in ?? ()
>(gdb) f
>#0  0xb6a63cc8 in ?? ()
>(gdb) info f
>Stack level 0, frame at 0xbefff618:
> pc = 0xb6a63cc8; saved pc = 0xb6a5feb0
> called by frame at 0xbefff618
> Arglist at 0xbefff618, args:
> Locals at 0xbefff618, Previous frame's sp is 0xbefff618
>(gdb) info args
>No symbol table info available.
>(gdb) info local
>No symbol table info available.
>(gdb) info source
>Current source file is ./Modules/python.c
>Compilation directory is /bld/pyt/cpython-android
>Located in /bld/pyt/cpython-android/Modules/python.c
>Contains 80 lines.
>Source language is c.
>Compiled with DWARF 2 debugging format.
>Does not include preprocessor macro info.
>Python tracker <rep...@bugs.python.org>


Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list

Reply via email to