Ah. Thanks for the tip. (How *was* I supposed to figure this out?
Installing python-dbg does seem to give 'gdb python' access to
python's own symbols, like other -dbg packages do; it never occurred
to me that it would have more magic than that...)
But, there still seems to be something wrong:
~$ python-dbg
Python 2.4.4 (#2, Jan 3 2008, 13:59:28)
[GCC 4.2.3 20071123 (prerelease) (Debian 4.2.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gobject
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File
"/var/lib/python-support/python2.4/gtk-2.0/gobject/__init__.py", line
30, in ?
from gobject.constants import *
File
"/var/lib/python-support/python2.4/gtk-2.0/gobject/constants.py", line
22, in ?
from _gobject import type_from_name
ImportError:
/var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject_d.so:
undefined symbol: Py_InitModule4
[33547 refs]
>>>
(Before trying this I moved things back to how they were before I did
my hack, and then did 'aptitude reinstall python-gobject{,-dbg}' just
to make sure. Strangely, though, when I renamed _gobject_d.so to
_gobject.so, and imported it with plain ol' non-dbg python, it worked
fine.)
Thanks,
-- Nathaniel
--
Electrons find their paths in subtle ways.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
