Subject: bug#47641: linphone segfaults when receiving messages from a Linphone account

From: Maxim Cournoyer <[email-masked]>
Date: Wed, 01 Sep 2021 13:00:04 -0400

Hello,

Maxim Cournoyer <[email-masked]> writes:

[...]

> When I checked Linphone's output today, it had crashed, with the
> following message:
>
> [...]
>
> [18:34:28:335][Info]Core:linphone: channel [0x2a9a6f0] [278] bytes parsed
> [18:34:28:335][Info]Core:linphone: Found transaction matching response.
> [18:34:28:335][Info]Core:linphone: Changing [client] [MESSAGE] transaction [0x426f760], from state [PROCEEDING] to [COMPLETED]
> [18:34:28:337][Error]Core:linphone: Unhandled generic exception in MainDb::getEventFromKey: `std::bad_cast`.
> [18:34:28:337][Error]Core:linphone: cannot find eventLog for db key [0x3a5bdb0] associated to message [0x3a5bd70]
> [18:34:28:338][Error]Core:linphone: Unhandled generic exception in MainDb::getEventFromKey: `std::bad_cast`.
> Segmentation fault

I've opened an issue with upstream:
https://gitlab.linphone.org/BC/public/linphone-desktop/-/issues/28.

Maxim