From owner-freebsd-stable Sat Oct 12 23:53: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEA7037B401; Sat, 12 Oct 2002 23:52:58 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDB8D43E97; Sat, 12 Oct 2002 23:52:57 -0700 (PDT) (envelope-from marcus@FreeBSD.org) Received: from gyros (gyros.marcuscom.com [192.168.1.9]) by creme-brulee.marcuscom.com (8.12.6/8.12.6) with ESMTP id g9D6qr01003433; Sun, 13 Oct 2002 02:52:53 -0400 (EDT) (envelope-from marcus@FreeBSD.org) Subject: Re: gaim 0.59.4_1 segfaulting in 4.7-stable From: Joe Marcus Clarke To: Kenneth W Cochran Cc: freebsd-ports@FreeBSD.org, freebsd-stable@FreeBSD.org In-Reply-To: <200210130608.CAA60834123@shell.TheWorld.com> References: <200210130608.CAA60834123@shell.TheWorld.com> Content-Type: multipart/mixed; boundary="=-f3D/OmZZ/AaSkpYlfpYr" X-Mailer: Ximian Evolution 1.0.8 Date: 13 Oct 2002 02:52:24 -0400 Message-Id: <1034491944.347.23.camel@gyros.marcuscom.com> Mime-Version: 1.0 X-Spam-Status: No, hits=-5.1 required=5.0 tests=AWL,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, SPAM_PHRASE_00_01 version=2.41 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-f3D/OmZZ/AaSkpYlfpYr Content-Type: text/plain Content-Transfer-Encoding: 7bit On Sun, 2002-10-13 at 02:08, Kenneth W Cochran wrote: > Hello: > > I'm getting signal 6 & coredumps with gaim-esound-0.59.4_1 > in 4.7-stable as of 2002/10/12. The ports tree is also > up to date with the rest of the OS. > > End of gdb trace as follows: > > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > Program received signal SIGSEGV, Segmentation fault. > 0x285e528c in strncasecmp () from /usr/lib/libc.so.4 > (gdb) bt > #0 0x285e528c in strncasecmp () from /usr/lib/libc.so.4 > #1 0x282bd3ca in g_strncasecmp () from /usr/local/lib/libglib12.so.3 > #2 0x28655da0 in yahoo_process_notify () from /usr/X11R6/lib/gaim/libyahoo.so > #3 0x28656c3a in yahoo_packet_process () from /usr/X11R6/lib/gaim/libyahoo.so > #4 0x28656ea4 in yahoo_pending () from /usr/X11R6/lib/gaim/libyahoo.so > #5 0x80a9098 in gaim_io_invoke () > #6 0x282b1991 in g_io_unix_dispatch () from /usr/local/lib/libglib12.so.3 > #7 0x282b3137 in g_main_dispatch () from /usr/local/lib/libglib12.so.3 > #8 0x282b3765 in g_main_iterate () from /usr/local/lib/libglib12.so.3 > #9 0x282b3918 in g_main_run () from /usr/local/lib/libglib12.so.3 > #10 0x281cc956 in gtk_main () from /usr/X11R6/lib/libgtk12.so.2 > #11 0x805c6fd in main () > #12 0x805a6a5 in _start () > (gdb) > > This appears to only be happing with Yahoo. I'd think if some > limit were being exceeded, at least it should crash somewhat > gracefully & not completely exit & coredump {shrug}. > > So far, I haven't found any recent "obvious" base system > updates that that might be causing this. Also, gaim has > never failed here in such a messy way. > > Any ideas? How to fix/workaround? Yep. Looks like a known issue. Here is a fix from gaim's CVS. I'll be committing this shortly. Joe > > Thanks, > > -kc > -- Joe Marcus Clarke FreeBSD GNOME Team :: marcus@FreeBSD.org http://www.FreeBSD.org/gnome --=-f3D/OmZZ/AaSkpYlfpYr Content-Disposition: attachment; filename=patch-temp Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; name=patch-temp; charset=ISO8859-1 --- src/protocols/yahoo/yahoo.c.orig Sun Oct 13 02:50:25 2002 +++ src/protocols/yahoo/yahoo.c Sun Oct 13 02:50:58 2002 @@ -525,6 +525,9 @@ l =3D l->next; } =09 + if (!msg) + return; + if (!g_strncasecmp(msg, "TYPING", strlen("TYPING"))) { if (*stat =3D=3D '1') serv_got_typing(gc, from, 0); --=-f3D/OmZZ/AaSkpYlfpYr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message