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

[Antoine Beaupré]

On 2023-03-19 17:32:02, Giuseppe Bilotta wrote:
> 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  0x7f47993106d1 mastodon_status_show_chat (mastodon.so + 0xe6d1)
> #1  0x7f4799310ff8 mastodon_http_timeline (mastodon.so + 0xeff8)
> #2  0x56291351f129 http_incoming_data (bitlbee + 0x29129)
> #3  0x56291351dfc8 gaim_io_invoke (bitlbee + 0x27fc8)
> #4  0x7f47a409867f g_main_context_dispatch (libglib-2.0.so.0 + 0x5467f)
> #5  0x7f47a4098a38 n/a (libglib-2.0.so.0 + 0x54a38)
> #6  0x7f47a4098cef g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
> #7  0x562913506c87 main (bitlbee + 0x10c87)
> #8  0x7f47a39b918a __libc_start_call_main (libc.so.6 + 0x2718a)
> #9  0x7f47a39b9245 __libc_start_main_impl (libc.so.6 + 0x27245)
> #10 0x56291350728a _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.

Thanks for the report. Would you be so kind as to generate a back trace
with debugging symbols enabled?

-- 
The Net treats censorship as damage and routes around it.
 - John Gilmore

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

[Giuseppe Bilotta]

Package: bitlbee-plugin-mastodon
Version: 1.4.5-1
Severity: important

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  0x7f47993106d1 mastodon_status_show_chat (mastodon.so + 0xe6d1)
#1  0x7f4799310ff8 mastodon_http_timeline (mastodon.so + 0xeff8)
#2  0x56291351f129 http_incoming_data (bitlbee + 0x29129)
#3  0x56291351dfc8 gaim_io_invoke (bitlbee + 0x27fc8)
#4  0x7f47a409867f g_main_context_dispatch (libglib-2.0.so.0 + 0x5467f)
#5  0x7f47a4098a38 n/a (libglib-2.0.so.0 + 0x54a38)
#6  0x7f47a4098cef g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
#7  0x562913506c87 main (bitlbee + 0x10c87)
#8  0x7f47a39b918a __libc_start_call_main (libc.so.6 + 0x2718a)
#9  0x7f47a39b9245 __libc_start_main_impl (libc.so.6 + 0x27245)
#10 0x56291350728a _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.



-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'testing-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bitlbee-plugin-mastodon depends on:
ii  bitlbee-libpurple  3.6-1.3
ii  libc6  2.36-8
ii  libglib2.0-0   2.74.6-1

bitlbee-plugin-mastodon recommends no packages.

bitlbee-plugin-mastodon suggests no packages.

-- no debconf information