Date: Tue, 02 May 2006 23:09:02 -0300 From: Rainer Alves <rainer.alves@gmail.com> To: ports@freebsd.org Subject: Gaim broken after Glib 2.10 upgrade Message-ID: <445810BE.9090304@gmail.com>
next in thread | raw e-mail | index | archive | help
After updating Gnome to 2.14 and Glib to 2.10, GAIM is now broken and segfaults whenever I try to establish a connection. Rebuilding all gaim dependecies didn't help. [rainer@bsd ~]$ uname -a FreeBSD bsd.powered.net 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Sat Apr 22 14:17:16 BRST 2006 root@bsd.powered.net:/usr/obj/usr/src/sys/RAINER i386 [Switching to Thread 0x82502e0 (LWP 100113)] 0x286cb9d7 in g_slice_alloc () from /usr/local/lib/libglib-2.0.so.0 (gdb) bt #0 0x286cb9d7 in g_slice_alloc () from /usr/local/lib/libglib-2.0.so.0 #1 0x286cbdd9 in g_slist_prepend () from /usr/local/lib/libglib-2.0.so.0 #2 0x286ce18c in g_strsplit () from /usr/local/lib/libglib-2.0.so.0 #3 0x28eae47d in msn_command_from_string (string=0x0) at command.c:60 #4 0x28eae37d in msn_cmdproc_process_cmd_text (cmdproc=0x84a02a0, command=0x862e5b8 "LST carlossfreitas@hotmail.com Carlos%20Freitas 11 1") at cmdproc.c:333 #5 0x28eb911d in read_cb (data=0x8218300, source=12, cond=GAIM_INPUT_READ) at servconn.c:385 #6 0x080badab in gaim_gtkdialogs_remove_chat () #7 0x286db133 in g_vasprintf () from /usr/local/lib/libglib-2.0.so.0 #8 0x286b7895 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0 #9 0x286b9135 in g_main_context_acquire () from /usr/local/lib/libglib-2.0.so.0 #10 0x286b9390 in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.0 #11 0x2823d74b in gtk_main () from /usr/X11R6/lib/libgtk-x11-2.0.so.0 #12 0x080dff8e in main () This seems like a memory allocation problem (perhaps related to jemalloc in current?). This particular function (g_slice_alloc) was added in 2.10, as noted here: http://developer.gnome.org/doc/API/2.0/glib/glib-Memory-Slices.html#id3343782 Here's what the GLIB docs also say: "Note that the underlying slice allocation mechanism can be changed with the G_SLICE=always-malloc environment variable." That's exactly what I did, and the problem was solved. Perhaps this tip should be included somewhere, as I'm sure other CURRENT users will be affected. -- Rainer Alves
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?445810BE.9090304>