From: raingloom <raingloom@riseup.net>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: help-guix@gnu.org
Subject: Re: Help with fixing seg-fault in telegram
Date: Mon, 25 Jan 2021 18:28:11 +0100 [thread overview]
Message-ID: <20210125182811.50c3c316@riseup.net> (raw)
In-Reply-To: <e2a963a1-3c7b-77e3-2ca1-3905f4b9957e@raghavgururajan.name>
On Fri, 22 Jan 2021 00:30:12 -0500
Raghav Gururajan <rg@raghavgururajan.name> wrote:
> Hello Folks!
>
> I am stuck with telegram-desktop segfaulting while answering calls.
>
> STEPS TO REPRODUCE:
> [1] Apply attached diff file on top of master
> (296156d9d1def88ccfda7d46cdcb574a4a52947b).
> [2] Install telegram-desktop.
> [3] Login and make/answer calls.
>
> Here is the gdb trace: https://paste.debian.net/plain/1182169
>
> Any ideas please?
>
> Regards,
> RG.
It may be a good idea to show this stack trace to the Telegram
developers as well.
prev parent reply other threads:[~2021-01-25 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 5:30 Help with fixing seg-fault in telegram Raghav Gururajan
2021-01-25 17:28 ` raingloom [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210125182811.50c3c316@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=rg@raghavgururajan.name \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).