From: "Tobias S. Predel" <tobias.predel@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Bluez 5.56 segfaulting while A2DP
Date: Fri, 26 Feb 2021 16:12:19 +0100 [thread overview]
Message-ID: <YDkP07ts5xokM1um@t2b3> (raw)
Dear all,
I experienced a SEGFAULT from bluez 5.56-1
on Arch Linux - linux 5.11.1.arch1-1:
It happened during having A2DP connection with pipewire-git 0.3.22.76.g08445d2c-1.
This is the backtrace:
# coredumpctl debug
(gdb) thread apply all bt
Thread 1 (Thread 0x7fb8325f67c0 (LWP 663)):
#0 0x00007fb832c74f19 in __strcasecmp_l_avx () from /usr/lib/libc.so.6
#1 0x000055d78e38c3b1 in play_status_to_val (status=0x0) at profiles/audio/avrcp.c:729
#2 0x000055d78e38ce3e in avrcp_player_event (player=player@entry=0x55d78f058a20, id=<optimized out>, data=data@entry=0x0) at profiles/audio/avrcp.c:807
#3 0x000055d78e38ced6 in avrcp_player_event (data=0x0, id=<optimized out>, player=0x55d78f058a20) at profiles/audio/avrcp.c:783
#4 notify_addressed_player_changed (user_data=user_data@entry=0x55d78f058a20) at profiles/audio/avrcp.c:1804
#5 0x000055d78e3906ad in avrcp_unregister_player (player=0x55d78f058a20) at profiles/audio/avrcp.c:4452
#6 0x000055d78e3830c8 in media_player_remove (data=0x55d78f050ff0) at profiles/audio/media.c:1052
#7 unregister_player (conn=<optimized out>, msg=0x55d78f0079d0, data=<optimized out>) at profiles/audio/media.c:1902
#8 0x000055d78e404fe9 in process_message (connection=0x55d78f005e00, message=0x55d78f0079d0, method=0x55d78e47b778 <media_methods+120>, iface_user_data=<optimized out>) at gdbus/object.c:246
#9 0x00007fb832df17d6 in ?? () from /usr/lib/libdbus-1.so.3
#10 0x00007fb832de13bd in dbus_connection_dispatch () from /usr/lib/libdbus-1.so.3
#11 0x000055d78e401681 in message_dispatch (data=0x55d78f005e00) at gdbus/mainloop.c:59
#12 0x00007fb832e72b84 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0x00007fb832ec6c21 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007fb832e720d3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#15 0x000055d78e41acc6 in mainloop_run () at src/shared/mainloop-glib.c:66
#16 0x000055d78e41b148 in mainloop_run_with_signal (func=func@entry=0x55d78e3acf70 <signal_callback>, user_data=user_data@entry=0x0) at src/shared/mainloop-notify.c:188
#17 0x000055d78e36fac0 in main (argc=<optimized out>, argv=<optimized out>) at src/main.c:1084
Regards,
Tobias Predel
--
La perfection est atteinte, non pas lorsqu'il n'y a plus rien à ajouter,
mais lorsqu'il n'y a plus rien à retirer. — Antoine de Saint-Exupéry
next reply other threads:[~2021-02-26 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 15:12 Tobias S. Predel [this message]
2021-02-26 21:22 ` Bluez 5.56 segfaulting while A2DP Luiz Augusto von Dentz
2021-02-27 8:53 ` Tobias S. Predel
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=YDkP07ts5xokM1um@t2b3 \
--to=tobias.predel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.