telepathy-gabble crashed with SIGSEGV in gabble_request_pipeline_enqueue()

StacktraceTop:
 gabble_request_pipeline_enqueue (pipeline=0x0,
 request_send (request=0x8fc4680,
 gabble_vcard_manager_request (self=0x8fb8040, handle=32,
 aliases_request_basic_pep_cb (self=0x8fb4250, msg=0x0,
 pep_request_cb (conn=0x8fb4250, msg=0x0,

There are indeed plenty of null pointers here, so fixing this might be easy. Ken, can you please look at this at some point, or bounce back to canonical-desktop-team if you don't have time? Thanks!

This is still happening on pretty much a daily basis

@mdz: I haven't been able to reproduce this, can you test this deb for me?

http://people.canonical.com/~kenvandine/telepathy-gabble_0.11.4-1ubuntu1~ppa1_i386.deb

This is a natty i386 build, let me know if that netbook is still maverick and I'll build for maverick.

On Mon, Dec 20, 2010 at 10:05:57PM -0000, Ken VanDine wrote:
> @mdz: I haven't been able to reproduce this, can you test this deb for
> me?
>
> http://people.canonical.com/~kenvandine/telepathy-
> gabble_0.11.4-1ubuntu1~ppa1_i386.deb
>
> This is a natty i386 build, let me know if that netbook is still
> maverick and I'll build for maverick.

It's still running 10.10, so I'll need a maverick binary (or a patch).

What changes are included in this package?

--
 - mdz

I have the test package installed on the same system where I originally reported this bug (though I see it on this system as well).

As requested on IRC, I'll record the output of "gconftool --dump /apps/empathy" after the crash.

telepathy-gabble crashed again this morning when I resumed my netbook, but this time with what looks like a failed assertion:

#0 0x0091f416 in __kernel_vsyscall ()
#1 0x0071d941 in raise () from /lib/libc.so.6
#2 0x00720e42 in abort () from /lib/libc.so.6
#3 0x00cd04af in g_assertion_message () from /lib/libglib-2.0.so.0
#4 0x00cd0aed in g_assertion_message_expr () from /lib/libglib-2.0.so.0
#5 0x080f09da in ?? ()
#6 0x00a70d91 in ?? () from /usr/lib/libgobject-2.0.so.0
#7 0x00c902aa in g_datalist_id_set_data_full () from /lib/libglib-2.0.so.0
#8 0x00a713d9 in ?? () from /usr/lib/libgobject-2.0.so.0
#9 0x00b76f7e in tp_base_connection_dispose (object=0x8e9b250)
    at base-connection.c:572

I redirected empathy's stdout and stderr to a file, but the error message didn't turn up there. I also didn't find anything in ~/.xsession-errors. Looking at a running telepathy-gabble process, file descriptors 0-2 are all /dev/null, so it looks like the error message has been lost.

Please look at the debug log in empathy, In the empathy menu, Help->Debug. You can narrow the messages to gabble and save them to a file.

On Wed, Dec 22, 2010 at 01:47:20PM -0000, Ken VanDine wrote:
> Please look at the debug log in empathy, In the empathy menu,
> Help->Debug. You can narrow the messages to gabble and save them to a
> file.

I've sent the debug log to you separately.

--
 - mdz

I built telepathy-gabble with DEB_BUILD_OPTIONS="noopt nostrip" and got the following complete backtrace:

#0 0x00000000004aee0f in gabble_request_pipeline_enqueue (pipeline=0x0,
    msg=0x126c400, timeout=180, callback=0x4bf90d <pipeline_reply_cb>,
    user_data=0x18e5a10) at request-pipeline.c:406
        priv = 0x1892ac0
        item = 0x122a900
        __PRETTY_FUNCTION__ = "gabble_request_pipeline_enqueue"
#1 0x00000000004bffff in request_send (request=0x18e5a10, timeout=180)
    at vcard-manager.c:1519
        jid = 0x18c7230 "bobdobbs@2entwine.net"
        msg = 0x126c400
        entry = 0x1892ac0
        conn = 0x125a0d0
        base = 0x125a0d0
        contact_repo = 0x1239460
        __PRETTY_FUNCTION__ = "request_send"
#2 0x00000000004c01fc in gabble_vcard_manager_request (self=0x1255430,
    handle=31, timeout=180, callback=0, user_data=0x0, object=0x125a0d0)
    at vcard-manager.c:1579
        priv = 0x1255450
        connection = 0x125a0d0
        contact_repo = 0x1239460
        request = 0x18e5a10
        entry = 0x1892ac0
        __PRETTY_FUNCTION__ = "gabble_vcard_manager_request"
#3 0x0000000000470eb2 in aliases_request_basic_pep_cb (self=0x125a0d0,
    msg=0x0, user_data=0x1f, error=0x7fffcb695f30) at conn-aliasing.c:259
        source = GABBLE_CONNECTION_ALIAS_FROM_JID
        handle = 31
#4 0x0000000000471135 in pep_request_cb (conn=0x125a0d0, msg=0x0,
    user_data=0x18e4980, error=0x7fffcb695f30) at conn-aliasing.c:326
        ctx = 0x18e4980
#5 0x00000000004ae79b in gabble_request_pipeline_dispose (object=0x122a900)
    at request-pipeline.c:247
        self = 0x122a900
        priv = 0x122a920
        disconnected = {domain = 626, code = 5,
          message = 0x5430e0 "Request failed because connection became disconnected"}
        item = 0x1935b60
        __PRETTY_FUNCTION__ = "gabble_request_pipeline_dispose"
#6 0x00007f653eee8d8a in g_object_unref () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#7 0x0000000000474f66 in gabble_connection_dispose (object=0x125a0d0)
    at connection.c:1105
        _tp_clear_pointer_tmp = 0x122a900
        self = 0x125a0d0
        base = 0x125a0d0
        priv = 0x125a2e0
        __PRETTY_FUNCTION__ = "gabble_connection_dispose"
#8 0x00007f653eee8d8a in g_object_unref () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#9 0x00000000004f67ce in pep_reply_cb (source=0x126c190, res=0x129d120,
    user_data=0x125a0d0) at conn-location.c:106
        conn = 0x125a0d0
        reply_msg = 0x0
        error = 0x18d66b0
        from = 0x122fac0 ""
        __PRETTY_FUNCTION__ = "pep_reply_cb"
#10 0x00000000004cf334 in send_query_cb (source=0x15703c0, res=0x129d180,
    user_data=0x129d120) at wocky-pep-service.c:296
        result = 0x129d120
        error = 0x18d6640
        reply = 0x0
#11 0x00007f653f3acbb9 in ?? () from /usr/lib/libgio-2.0.so.0
No symbol table info available.
#12 0x00007f653e420342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
No symbol table info available.
#13 0x00007f653e4242a8 in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#14 0x00007f653e4247b5 in g_main_loop_run () from /lib/libgl...

@mdz: Can you try this patch out?

@mdz: can you try http://people.canonical.com/~kenvandine/telepathy-gabble_0.10.0-1ubuntu1~ppa1_i386.deb

On Tue, Jan 11, 2011 at 07:11:57PM -0000, Ken VanDine wrote:
> @mdz: can you try http://people.canonical.com/~kenvandine/telepathy-
> gabble_0.10.0-1ubuntu1~ppa1_i386.deb

I just experienced my first crash since installing this version. I'm
offline at the moment, so I can't upload the crash dump yet, but will do so
when I get back online.

Oddly, I don't see any messages in the debug log from gabble (only
mission-control, Empathy.FileTransfer and Logger.

--
 - mdz

I've filed the crash as bug 702063

the issue should be fixed in the natty version but feel free to reopn if you get it again