Red Hat Bugzilla – Bug 552654
"ValueError: variable 'g_quarks' not found" exceptions raised by GObject gdb-archer pretty-printer
Last modified: 2010-12-03 19:49:51 EST
Description of problem:
Attachment 381817 [details] to bug 552651 shows a backtrace of a PyGTK app.
This backtrace contains numerous python backtraces from gdb itself, from inside the GObject prettyprinter:
See e.g. frame #7 in that backtrace:
#7 0x0000003c6c4099b9 in panel_applet_control_bound (
control=<value optimized out>, applet=Traceback (most recent call last):
File "/usr/share/glib-2.0/gdb/gobject.py", line 72, in to_string
name = g_type_name_from_instance (self.val)
File "/usr/share/glib-2.0/gdb/gobject.py", line 59, in g_type_name_from_instance
name = g_type_to_name (gtype)
File "/usr/share/glib-2.0/gdb/gobject.py", line 26, in g_type_to_name
return glib.g_quark_to_string (typenode["qname"])
File "/usr/share/glib-2.0/gdb/glib.py", line 13, in g_quark_to_string
val = read_global_var ("g_quarks")
File "/usr/share/glib-2.0/gdb/glib.py", line 5, in read_global_var
ValueError: variable 'g_quarks' not found
) at panel-applet.c:1394
ret = <value optimized out>
__PRETTY_FUNCTION__ = "panel_applet_control_bound"
Version-Release number of selected component (if applicable):
(Luke Macken's machine; CCing him):
Not sure, but I'm fairly sure I've seen this in other ABRT reports for other PyGTK apps.
Alex, any idea ?
Is the glib debuginfo installed?
The python code tries to look up the g_quarks global inside glib, but if debug symbols are missing i guess that may fail. We should make the python code handle the symbol lookup failing in a nicer way.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.