[Rtcomm] [Rtcomm] [Bug 3455] telepathy-gabble deadlooping
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Tue Feb 17 22:01:41 EET 2009
- Previous message: [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
- Next message: [Rtcomm] Your Bugzilla buglist needs attention.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=3455 ------- Comment #8 from maemo at subs.maneos.org 2009-02-17 22:01 GMT+3 ------- Created an attachment (id=1126) --> (https://bugs.maemo.org/attachment.cgi?id=1126&action=view) rich core dump of telepathy-gabble during looping (In reply to comment #7) > You don't get them just by: > apt-get install libglib2.0-0-dbg libtelepathy-glib0-dbg > ? Never mind, I naively assumed they'd be in the same repository as the glibc ones. After enabling the SDK repo they installed fine. Still missing symbols for some libs (libssl, libcrypto, libz, libdb1) but the stack trace is more complete now: (gdb) bt #0 0x41089f3c in malloc_consolidate () from /lib/libc.so.6 #1 0x4108aef0 in _int_malloc () from /lib/libc.so.6 #2 0x4108c13c in calloc () from /lib/libc.so.6 #3 0x41082934 in open_memstream () from /lib/libc.so.6 #4 0x410d9e2c in __vsyslog_chk () from /lib/libc.so.6 #5 0x410da3f8 in syslog () from /lib/libc.so.6 #6 0x411776ec in IA__g_log_default_handler (log_domain=0x4119f7c4 "default", log_level=G_LOG_LEVEL_DEBUG, message=0x715b0 "no connections, and timed out", unused_data=0x411a5520) at gmessages.c:990 #7 0x4117696c in IA__g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_DEBUG, format=0x42240960 "no connections, and timed out", args1=0xbed3e414) at gmessages.c:479 #8 0x41176be8 in IA__g_log ( log_domain=0x411370cc "�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A�p\023A\004q\023A\004q\023A\fq\023A\fq\023A\024q\023A\024q\023A\034q\023A\034q\023A$q\023A$q\023A,q\023A,q\023A4q\023A4q\023A<q\023A<q\023ADq\023ADq\023ALq\023ALq\023ATq\023ATq\023A\\q\023A\\q\023Adq\023Adq\023Alq\023Alq\023Atq\023Atq\023A|q\023A|q\023A\204q\023A\204q\023A"..., log_level=1092244828, format=0x42240960 "no connections, and timed out") at gmessages.c:522 #9 0x42235ef0 in kill_connection_manager (data=0x411370cc) at run.c:67 #10 0x41171498 in g_timeout_dispatch (source=0x70498, callback=0x42235eb5 <kill_connection_manager+1>, user_data=0x41136030) at gmain.c:3422 #11 0x4116e108 in IA__g_main_context_dispatch (context=0x64a80) at gmain.c:2045 #12 0x4116ffd4 in g_main_context_iterate (context=0x64a80, block=1, dispatch=1, self=0x0) at gmain.c:2677 #13 0x4117034c in IA__g_main_loop_run (loop=0x634d8) at gmain.c:2881 #14 0x42236076 in tp_run_connection_manager (prog_name=0x0, version=0x451f4 "0.6.2.1", construct_cm=0x4224ee70 <manager>, argc=0, argv=0xbed3e6b4) at run.c:235 #15 0x00010034 in ?? () Cannot access memory at address 0x0 (In reply to comment #5) > Alternatively you could force the process to core-dump after installing > sp-rich-core from the tools repository & creating "core-dumps" directory to a > memory card with at least few MBs of free space. You can then attach the core > dump to this bug. Attached. > (the compressed rich core dumps can be extracted with a tool > from sp-rich-core-postproc e.g. to check that they don't contain any sensitive > information you wouldn't want to attach to public bugzilla) The core dump contains the account password. I tried to create one with a dummy account but couldn't reproduce anymore. After a few more tests it seems that the infinite loop only triggers when the configured server has AAAA records, and it goes away if I insmod ipv6.ko. I think I may be chasing a different bug to the one originally reported (gtalk.com doesn't advertise AAAA RRs, at least currently). -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email Replies to this email are NOT read, instead please add comments at https://bugs.maemo.org/show_bug.cgi?id=3455 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
- Previous message: [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
- Next message: [Rtcomm] Your Bugzilla buglist needs attention.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]