2.6.2 segfaulting

[Ted Creedon]

Noticed this on startup:

Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0
Try: zypper install -C
"debuginfo(build-id)=a3f8edc19f47fd2290dbbf3d05670ed13ba6a93c"
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
Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0
T


On Mon, Mar 3, 2014 at 4:12 PM, Ted Creedon <tcreedon at easystreet.net> wrote:

> do I need a pointer to the sources for
>
> libgobject-2_0-0 - General-Purpose Utility Library -- Object-Oriented
> Framework for C?
>
>
>
>
> On Mon, Mar 3, 2014 at 3:47 PM, John Ralls <jralls at ceridwen.us> wrote:
>
>>
>> On Mar 3, 2014, at 3:30 PM, Ted Creedon <tcreedon at easystreet.net> wrote:
>>
>> > Program received signal SIGSEGV, Segmentation fault.
>> > 0x00007fffef356cac in g_type_check_instance_is_a () from
>> > /usr/lib64/libgobject-2.0.so.0
>> >
>> >
>> > can't do a bt because the fault freezes the X Screen
>> >
>> > had to ssh in from another box & kill -TERM gdb
>> >
>> > Should I do a debug build?
>>
>> Yes, of course. You'll also want the symbols and sources at least for
>> glib.
>>
>> Regards,
>> John Ralls
>>
>>
>