From: "Amisha Jain (QUIC)" <quic_amisjain@quicinc.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: MAP server crash during connection
Date: Fri, 31 May 2024 07:04:25 +0000 [thread overview]
Message-ID: <ec4a4adbfee94a699ebd635abc51f01c@quicinc.com> (raw)
Hi bluez team,
I have been trying to verify MAP Server obex profile on bluez 5.65.
While trying connection, I have noticed the crash on the server side (connection initiated from client side) and hence connection is failing.
Please find the backtrace of the crash -
assertion failed "i == len" file "../../dbus-1.14.8/dbus/dbus-object-tree.c" line 1321 function _dbus_decompose_path
/usr/lib/libdbus-1.so.3(_dbus_print_backtrace+0x28) [0xfffff7f4cc9c]
/usr/lib/libdbus-1.so.3(_dbus_abort+0x14) [0xfffff7f4fe3c]
/usr/lib/libdbus-1.so.3(+0x4a9cc) [0xfffff7f3a9cc]
/usr/lib/libdbus-1.so.3(+0x36c5c) [0xfffff7f26c5c]
/usr/lib/libdbus-1.so.3(dbus_connection_get_object_path_data+0xc4) [0xfffff7f0f818]
/usr/libexec/bluetooth/obexd(g_dbus_emit_property_changed_full+0x30) [0x450dc4]
/usr/libexec/bluetooth/obexd(g_dbus_emit_property_changed+0x14) [0x450ec0]
/usr/libexec/bluetooth/obexd(manager_emit_transfer_property+0x34) [0x429408]
/usr/libexec/bluetooth/obexd(obex_put_stream_start+0xc8) [0x42b314]
/usr/libexec/bluetooth/obexd() [0x425f58]
/usr/libexec/bluetooth/obexd() [0x42adcc]
/usr/libexec/bluetooth/obexd() [0x4171dc]
/usr/libexec/bluetooth/obexd() [0x418078]
/usr/lib/libglib-2.0.so.0(+0xb20cc) [0xfffff7e420cc]
/usr/lib/libglib-2.0.so.0(+0x54a30) [0xfffff7de4a30]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x44) [0xfffff7de850c]
/usr/lib/libglib-2.0.so.0(+0x5868c) [0xfffff7de868c]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1ac) [0xfffff7de8b08]
/usr/libexec/bluetooth/obexd(main+0x128) [0x427d6c]
/lib/libc.so.6(+0x2affc) [0xfffff7c0affc]
/lib/libc.so.6(__libc_start_main+0x90) [0xfffff7c0b0c4]
/usr/libexec/bluetooth/obexd(_start+0x30) [0x4101b0]
Program received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:4
Please help support the issue.
Thanks,
Amisha
next reply other threads:[~2024-05-31 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 7:04 Amisha Jain (QUIC) [this message]
2024-06-04 6:13 ` MAP server crash during connection Amisha Jain (QUIC)
2024-06-07 7:00 ` Amisha Jain (QUIC)
2024-06-07 14:10 ` Luiz Augusto von Dentz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec4a4adbfee94a699ebd635abc51f01c@quicinc.com \
--to=quic_amisjain@quicinc.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox