#1033204 bitlbee-plugin-mastodon: sporadically but consistently segfaults in unclear circumstances

Package:
bitlbee-plugin-mastodon
Source:
bitlbee-plugin-mastodon
Description:
Mastodon plugin for bitlbee IRC gateway
Submitter:
Giuseppe Bilotta
Date:
2023-03-20 00:39:04 UTC
Severity:
normal
#1033204#5
Date:
2023-03-19 16:32:02 UTC
From:
To:
In certain circumstances that I have yet been unable to fully clarify,
the plugin segfaults (bringing down all of bitlbee with it) while processing the timeline.
This is the relevant part of the backtrace as reported in the journal:

#0  0x00007f47993106d1 mastodon_status_show_chat (mastodon.so + 0xe6d1)
#1  0x00007f4799310ff8 mastodon_http_timeline (mastodon.so + 0xeff8)
#2  0x000056291351f129 http_incoming_data (bitlbee + 0x29129)
#3  0x000056291351dfc8 gaim_io_invoke (bitlbee + 0x27fc8)
#4  0x00007f47a409867f g_main_context_dispatch (libglib-2.0.so.0 + 0x5467f)
#5  0x00007f47a4098a38 n/a (libglib-2.0.so.0 + 0x54a38)
#6  0x00007f47a4098cef g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
#7  0x0000562913506c87 main (bitlbee + 0x10c87)
#8  0x00007f47a39b918a __libc_start_call_main (libc.so.6 + 0x2718a)
#9  0x00007f47a39b9245 __libc_start_main_impl (libc.so.6 + 0x27245)
#10 0x000056291350728a _start (bitlbee + 0x1128a)

When this happens, I have to stop bitlbee, wait an unspecified amount of time,
and then try restarting it hoping that th message responsible for the segfault
isn't in my timeline(s) anymore.

I'm afraid I still haven't been able to identify the kind of message(s) that cause the fault.
#1033204#10
Date:
2023-03-20 00:36:12 UTC
From:
To:
Thanks for the report. Would you be so kind as to generate a back trace
with debugging symbols enabled?
#1033204#15
Date:
2023-03-20 00:36:12 UTC
From:
To:
Thanks for the report. Would you be so kind as to generate a back trace
with debugging symbols enabled?