[ARMedslack] gdb python error

Thorsten Mühlfelder thenktor at gmx.de
Thu Apr 7 09:49:23 UTC 2011


Am Thursday 07 April 2011 09:30:10 schrieb Thorsten Mühlfelder:
> gdb shows this error on arm current:
>
> (gdb) run
> Starting program: /usr/bin/mpd -h
> [Thread debugging using libthread_db enabled]
> Traceback (most recent call last):
>   File
> "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.4-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
>
> It works on x86_64 current. So either I'm missing a dep (but cannot find
> the right one yet) or some other problem. Maybe different gdb configure
> options?

I have to correct myself: the x86_64 version shows the same error. On both 
arch it only comes up if the debugged program exits abnormally.

-- 
Thorsten Mühlfelder
Salix OS: www.salixos.org


More information about the ARMedslack mailing list