glib/glib/libglib-gdb.py.in

import sys
import gdb

# Update module path.
dir_ = '@datadir@/glib-2.0/gdb'
if not dir_ in sys.path:
    sys.path.insert(0, dir_)

from glib_gdb import register
register (gdb.current_objfile ())
Initial support for gdb python macros This includes support for gobject pointer pretty printing and signal frame compression in backtraces. https://bugzilla.gnome.org/show_bug.cgi?id=595619 2009-09-18 17:15:32 +02:00			`import sys`
			`import gdb`

			`# Update module path.`
Avoid shadowing dir builtin This is the same change that was already applied to the other gdb script we ship. I had forgotten there was a second one. 2010-12-03 14:39:59 -05:00			`dir_ = '@datadir@/glib-2.0/gdb'`
			`if not dir_ in sys.path:`
			`sys.path.insert(0, dir_)`
Initial support for gdb python macros This includes support for gobject pointer pretty printing and signal frame compression in backtraces. https://bugzilla.gnome.org/show_bug.cgi?id=595619 2009-09-18 17:15:32 +02:00
Rename gdb macros with `_gdb` suffix to avoid ns clashes glib installs a gdb helper file named `glib.py`. Then the "hook" file updates `sys.path` and does `import glib`. This will fail if glib has already been imported into gdb, say using `from gi.repository import GLib`. This is due to a namespace clash. One fix would be to rename the gdb helper files to not clash with other Python modules. This should be done for all such helper files. https://bugzilla.gnome.org/show_bug.cgi?id=760186 2016-05-23 10:45:55 -04:00			`from glib_gdb import register`
Initial support for gdb python macros This includes support for gobject pointer pretty printing and signal frame compression in backtraces. https://bugzilla.gnome.org/show_bug.cgi?id=595619 2009-09-18 17:15:32 +02:00			`register (gdb.current_objfile ())`