[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: caveat: GNOME 2.6 severly broken on Debian/unstable?



On Wed, Jun 02, 2004 at 12:34:52PM -0700, David Mosberger wrote:
> Be careful about upgrading to Debian/unstable at the moment!  It
> appears that GNOME 2.6 is completely broken for ia64.  From what I can
> tell, pretty much any GNOME app gets stuck in user-land.  For example,
> gdmlogin seems to get stuck in pango_xfg_get_font_map().  Anybody
> knows what's going on here?  (I should say I have only tried with a
> 2.6.6 kernel so far, though I doubt that matters.)

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252401

bit me when I wanted to use ethereal on a newly installed box ...

Basically, missing libraries on link of libpango

As for why it hangs and doesn't crash ... well if you disassemble it
you get (excuse the long lines)

0x2000000001f82590 <pango_xft_get_font_map+176>:        [MIB]       nop.m 0x0
0x2000000001f82591 <pango_xft_get_font_map+177>:                    nop.i 0x0
0x2000000001f82592 <pango_xft_get_font_map+178>:                    br.call.sptk.many b0=0x2000000001f82590 <pango_xft_get_font_map+176>;;

so it branches back to the start of it's bundle.  It should actually
be a call to g_object_new() I think, but as that's not defined at link
I guess the relocation never gets fixed up or something.

Someone who knows more about the toolchain might know exactly why.  I
would have thought it would be better to crash than tight loop with no
explaination.

-i
ianw@gelato.unsw.edu.au
http://www.gelato.unsw.edu.au

Attachment: signature.asc
Description: Digital signature


Reply to: