Hi,
I am compiling QuteCom RC2 on the latest Debian sid. On 64-bit, as soon
as I add an IM account, the application fails with a SIGABRT.

Does anyone have this problem?

GLib-ERROR **: /build/buildd/glib2.0-2.16.6/glib/gmem.c:136: failed to
allocate 68719476736 bytes
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x41d19950 (LWP 22258)]
0x00007f230cc6aed5 in raise () from /lib/libc.so.6
(gdb) bt
#0  0x00007f230cc6aed5 in raise () from /lib/libc.so.6
#1  0x00007f230cc6c3f3 in abort () from /lib/libc.so.6
#2  0x00007f23141cc44e in g_logv () from /usr/lib/libglib-2.0.so.0
#3  0x00007f23141cc4d3 in g_log () from /usr/lib/libglib-2.0.so.0
#4  0x00007f23141cabba in g_malloc () from /usr/lib/libglib-2.0.so.0
#5  0x00007f2310fdf8da in host_resolved (data=0x7f2300004560,
source=<value optimized out>, cond=<value optimized out>)
    at
/home/cavedon/svn/build-area/qutecom-2.2~rc2.dfsg0/libs/3rdparty/libpurple/pidgin-2.5.1/libpurple/dnsquery.c:586
#6  0x000000000082c2ec in purple_wg_io_invoke (source=<value optimized
out>, condition=<value optimized out>, data=0x7f230000a7f0)
    at
/home/cavedon/svn/build-area/qutecom-2.2~rc2.dfsg0/libs/imwrapper/src/purple/PurpleIMFactory.cpp:107
#7  0x00007f23141c278b in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#8  0x00007f23141c5f5d in ?? () from /usr/lib/libglib-2.0.so.0
#9  0x00007f23141c648d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#10 0x000000000082c5ca in PurpleMainEventLoop (data=<value optimized
out>) at
/home/cavedon/svn/build-area/qutecom-2.2~rc2.dfsg0/libs/imwrapper/src/purple/PurpleIMFactory.cpp:148
#11 0x00007f23141eb454 in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00007f230d93bfc7 in start_thread () from /lib/libpthread.so.0
#13 0x00007f230cd085ad in clone () from /lib/libc.so.6
#14 0x0000000000000000 in ?? ()

Note the size of the memory being allocated on the log message, there
must be some wrong casting inside libpurple...

Thanks,
Ludovico
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to