gnome-libs HEAD snapshot tarballs

[Martin Baulig <martin home-of-linux org>]

Hi guys,

already late at night and I'm very tired, so the long version
of this mail will follow tomorrow.

I've made some snapshot tarballs for gnome-libs HEAD.

* Availability:

        ftp://ftp.home-of-linux.org/pub/gnome-libs/

  (oh, btw. there is no gnome-libs tarball in that dir - this is because
   `make dist' currently doesn't work, but you should grab that from CVS
   anyways).

* Compile order

        glib pango gtk+ pkgconfig gnome-common gnome-xml ORBit oaf gconf
        gnome-vfs libart_lgpl gnome-libs

* Known problems:

  If you get some problem with a missing libgnomeui/gnomemarshal.h, just
  touch that file and then do a `make gnomemarshal.c'; this should regenarate
  that file. I fixed this in CVS but I don't know whether I really fixed it.

* Required configure arguments:

        # AUTOGEN_glib: --enable-debug=yes --enable-mem-check
        # AUTOGEN_gtk+: --enable-debug=yes
        # AUTOGEN_ORBit: --enable-platform-gnome-2
        # AUTOGEN_gconf: --enable-platform-gnome-2
        # AUTOGEN_gnome-vfs: --enable-platform-gnome-2
        # AUTOGEN_gnome-libs: --enable-compile-warnings=error
        # AUTOGEN_gnome-common: --enable-patform-gnome-2

Before you expect too much - this'll compile but crash immediately on startup;
I don't know the reason yet but I was able to put in some g_assert() in gmain.c
so that you'll at least get an assertion failed instead of a crash.

This will look like this:

---
Program received signal SIGSEGV, Segmentation fault.
0x406db9f0 in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0  0x406db9f0 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x4020e146 in g_source_attach (source=0x8069018, context=0x8064cb0) at gmain.c:758
#2  0x40505a83 in gdk_events_init () at gdkevents-x11.c:146
#3  0x404dc409 in gdk_init_check (argc=0xbffff864, argv=0xbffff860) at gdk.c:339
#4  0x4038cd62 in gtk_init_check (argc=0xbffff864, argv=0xbffff860) at gtkmain.c:216
#5  0x4038d72b in gtk_init (argc=0xbffff864, argv=0xbffff860) at gtkmain.c:484
#6  0x400acb0a in gtk_post_args_parse (app=0x804acf0, mod_info=0x40148140) at gnome-init.c:160
#7  0x407ca921 in gnome_program_postinit (app=0x804acf0) at gnomelib-init2.c:1303
#8  0x407ca9ff in gnome_program_initv (app_id=0x8049718 "selector_demo", app_version=0x8049714 "1.0", argc=1, 
    argv=0xbffff9e4, args=0xbffff924) at gnomelib-init2.c:1355
#9  0x407ca999 in gnome_program_init (app_id=0x8049718 "selector_demo", app_version=0x8049714 "1.0", argc=1, 
    argv=0xbffff9e4) at gnomelib-init2.c:1338
#10 0x80492bc in main (argc=1, argv=0xbffff9e4) at selector_demo.c:184
---

It looks like the problem is that it is passing NULL to pthread_mutex_lock()
(GLIBC 2.1).

The problem exists on both a recent Debian woody and on SuSE 7, so this shouln't
be local to my installation.

Happy debugging, more info's coming tomorrow.

-- 
Martin Baulig
martin gnome org (private)
baulig suse de (work)

_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers