Bug 1073284

I'm having this issue too on Fedora 20.

According to /usr/share/glib-2.0/gdb/gobject.py:

  import gdb
  import glib
  import gdb.backtrace
  import gdb.command.backtrace

The file seems to be the same in Fedora 19.

Trying the following commands on gdb prompt in Fedora 19 seems to indicate that gdb.backtrace nor gdb.command.backtrace exist.

(gdb) python import gdb                    # OK
(gdb) python import gdb.command            # OK
(gdb) python import gdb.command.backtrace  # failure
(gdb) python import gdb.backtrace          # failure

This problem might affect Fedora 19 too, but I haven't seen it yet.

I have the same problem on Fedora 20 KDE.

[donnie@fedora ~]$ gdb systemsettings
GNU gdb (GDB) Fedora 7.6.50.20130731-19.fc20
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
..
Reading symbols from /usr/bin/systemsettings...Reading symbols from /usr/bin/systemsettings...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install kde-workspace-4.11.8-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/systemsettings 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
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
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
Detaching after fork from child process 29207.
[Inferior 1 (process 29203) exited normally]
(gdb) quit

And I can confirm Yann Droneaud's observations.

(gdb) python import gdb
(gdb) python import gdb.command
(gdb) python import gdb.command.backtrace
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named backtrace
Error while executing Python code.
(gdb) python import gdb.backtrace
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named backtrace
Error while executing Python code.

*** This bug has been marked as a duplicate of bug 972351 ***