Wesley <nisp...@gmail.com> writes: > So, let me clarify here, in order to try, I get a clean machine. > > Centos 6.5 64bit. > Now , I try this: > 1. install gdb 7.7 from source , with configure option --with-python > > 2. install python 2.6.6 from source, with configure option --with-pydebug > > 3. run a python script > > 4. from command line, gdb python -p <pid> to attach the running script > > 5. within gdb, issue python, import libpython, end > no errors > 6. py-bt outputs nothing, py-locals says Unable to locate python frame > here is the snippet: > [root@localhost Python-2.6.6]# gdb python 52315 > GNU gdb (GDB) 7.7 > .... > Attaching to program: /home/nipen/test/Python-2.6.6/python, process 52315 > Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib64/ld-linux-x86-64.so.2 > 0x00000030a98e15c3 in ?? () > (gdb) bt > #0 0x00000030a98e15c3 in ?? () > #1 0x00007f4cf68d1219 in ?? () > #2 0x0000000000000000 in ?? ()
This looks like a very strange backtrace on C level as well. The most natural explanation would be: your process is in a very strange state (due to some C level problem). But, of course, your "gdb" might have general problems, as well. -- https://mail.python.org/mailman/listinfo/python-list
