Bug#246362: gaim segfaults when libc6-i686 is installed
On Wed, Apr 28, 2004 at 04:52:32PM +0100, Rui Tiago Cação Matos wrote:
> Package: libc6-i686
> Version: 2.3.2.ds1-12
>
> Here is the gdb log:
>
> GNU gdb 6.1-debian
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i386-linux"...(no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
>
> (gdb) run
> Starting program: /usr/bin/gaim
> (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
> [New Thread 1083169632 (LWP 2771)]
> (no debugging symbols found)...
> ### repeated many times ###
>
> Detaching after fork from child process 2776.
> (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...Detaching after fork from child process 2777.
> Detaching after fork from child process 2778.
> free(): invalid pointer 0x837baa8!
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1083169632 (LWP 2771)]
> 0x4068dbce in mallopt () from /lib/tls/i686/cmov/libc.so.6
> (gdb) bt
> #0 0x4068dbce in mallopt () from /lib/tls/i686/cmov/libc.so.6
> #1 0x40490e0a in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
> Previous frame inner to this frame (corrupt stack?)
>
> ------------------
>
> So i guess its libc6-i686 fault os is it gaim's?
A crash in malloc almost always indicates a bug in the program's memory
allocation. Try valgrind or similar.
I use gaim with libc6-i686 without any trouble.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
Reply to: