Created attachment 933148 [details] Extra install info Description of problem: I'm unable to backtrace anything, when I load something to debug, " Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace " Version-Release number of selected component (if applicable): Version : 7.7.1 Release : 18.fc20 How reproducible: Every case I try Steps to Reproduce: 1. Call gdb with a program passed as an arg 2. r 3. error ^ Actual results: The error shown above Expected results: Successful debug Additional info:
*** This bug has been marked as a duplicate of bug 972351 ***
(In reply to Ellis from comment #0) > I'm unable to backtrace anything, when I load something to debug, This is not correct - GDB still works as before including backtraces. It just prints the annoying warning.
Whenever I try to bt, I get an empty stack message every time.
Please provide a reproducer, works for me (that is it backtraces, it just prints that annoying warning at the top): $ gdb -batch -ex start -ex 'adv g_main_context_poll' -ex bt gtk-demo Temporary breakpoint 1 at 0x4112e0: file main.c, line 930. Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Temporary breakpoint 1, main (argc=1, argv=0x7fffffffdb58) at main.c:930 930 { [New Thread 0x7ffff1110700 (LWP 18446)] g_main_context_iterate (context=0x95c8c0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3708 3708 g_main_context_poll (context, timeout, max_priority, fds, nfds); #0 g_main_context_iterate (context=0x95c8c0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3708 #1 0x0000003647249a3a in g_main_loop_run (loop=0x95c980) at gmain.c:3907 [...] #48 0x0000000000426970 in create_text (buffer=buffer@entry=0x6352f0, is_source=is_source@entry=0) at main.c:750 #49 0x00000000004118d4 in main (argc=1, argv=0x7fffffffdb58) at main.c:967 I get very long backtrace. This is updates-testing Fedora 20 x86_64 but even updates Fedora 20 x86_64 should work the same. You mayneed to have the *-debuginfo.rpms installed to get the identical backtrace like above as GDB suggests you. But sure *-debuginfo.rpms do not have to be installed for the general backtracing issue you report here.
Hm everything seems to be fine now :| Sorry, feel free to close.