Github messages for voidlinux
 help / color / mirror / Atom feed
From: husio <husio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: telegram-desktop crashes
Date: Wed, 21 Jul 2021 12:02:05 +0200	[thread overview]
Message-ID: <20210721100205.D9eIJIvrouRfqDeSgq19qzQUzm0t45-5_FZ7bctmegw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32053@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]

New comment by husio on void-packages repository

https://github.com/void-linux/void-packages/issues/32053#issuecomment-884061779

Comment:
> Hi @husio, could you paste output of `~/.local/share/TelegramDesktop/log.txt`?

Sure, [log.txt](https://github.com/void-linux/void-packages/files/6854667/log.txt)

Found all the core dumps as well! :joy: 

```
% ls ~/.local/share/TelegramDesktop 
core.3616  core.3796  core.3869  core.4452  core.5016  core.5119  core.5189  core.5329  core.5401  tdata
core.3715  core.3806  core.3879  core.5006  core.5109  core.5179  core.5267  core.5391  log.txt
```

I don't know how to analyze a core dump file properly, here is some random output:
```
Core was generated by `telegram-desktop'.
Program terminated with signal SIGABRT, Aborted.
#0  __restore_sigs (set=set@entry=0x7fff0e593c50) at ./arch/x86_64/syscall_arch.h:40
40      ./arch/x86_64/syscall_arch.h: No such file or directory.
[Current thread is 1 (LWP 4069)]
(gdb) bt
#0  __restore_sigs (set=set@entry=0x7fff0e593c50) at ./arch/x86_64/syscall_arch.h:40
#1  0x00007fb5f293c620 in raise (sig=sig@entry=6) at src/signal/raise.c:11
#2  0x00007fb5f2904e20 in abort () at src/exit/abort.c:13
#3  0x000056521793908f in ?? ()
#4  0x000056521751b915 in ?? ()
#5  0x0000565217932eac in ?? ()
#6  0x00007fb5eb3d9edb in ?? () from /lib/libgiomm-2.4.so.1
#7  0x00007fb5e8c585ab in ?? () from /lib/libgio-2.0.so.0
#8  0x00007fb5e8a1669f in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#9  0x00007fb5e8a16a48 in ?? () from /lib/libglib-2.0.so.0
#10 0x00007fb5e8a16aff in g_main_context_iteration () from /lib/libglib-2.0.so.0
#11 0x00007fb5ea25916f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/libQt5Core.so.5
#12 0x00007fb5ea200dcb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/libQt5Core.so.5
#13 0x00007fb5ea209050 in QCoreApplication::exec() () from /lib/libQt5Core.so.5
#14 0x0000565216cfc695 in ?? ()
#15 0x0000565216cf14d1 in ?? ()
#16 0x0000565216cf16d4 in ?? ()
#17 0x00005652161efff5 in ?? ()
#18 0x00007fb5f290470a in libc_start_main_stage2 (main=0x5652161effc0, argc=1, argv=0x7fff0e594818) at src/env/__libc_start_main.c:94
#19 0x00005652161faa1a in ?? ()
#20 0x0000000000000001 in ?? ()
#21 0x00007fff0e59662e in ?? ()
#22 0x0000000000000000 in ?? ()
```

  parent reply	other threads:[~2021-07-21 10:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 11:33 [ISSUE] " husio
2021-07-20 12:24 ` ericonr
2021-07-20 17:23 ` husio
2021-07-20 17:28 ` husio
2021-07-20 18:23 ` ericonr
2021-07-20 18:28 ` ericonr
2021-07-20 18:40 ` husio
2021-07-20 18:53 ` ericonr
2021-07-20 18:53 ` ericonr
2021-07-20 19:09 ` husio
2021-07-20 19:23 ` ericonr
2021-07-20 19:23 ` ericonr
2021-07-21  7:45 ` krkk
2021-07-21  9:41 ` husio
2021-07-21  9:42 ` husio
2021-07-21  9:45 ` not-chicken
2021-07-21 10:02 ` husio [this message]
2021-07-21 10:16 ` not-chicken
2021-07-21 10:24 ` not-chicken
2021-07-22  7:50 ` slotThe
2021-07-22  9:08 ` ilya-fedin
2021-07-26 18:25 ` husio
2021-07-26 18:29 ` ilya-fedin
2021-07-26 18:30 ` ilya-fedin
2021-07-26 18:32 ` ilya-fedin
2021-08-02 18:11 ` Johnnynator
2021-08-02 18:51 ` husio
2021-08-02 18:53 ` husio
2021-09-12 10:30 ` Kratacoa
2021-09-12 15:39 ` Johnnynator
2021-09-21 15:04 ` Johnnynator
2021-09-21 15:31 ` slotThe
2021-09-21 15:48 ` [ISSUE] [CLOSED] " Johnnynator
2021-09-28 10:53 ` husio

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=20210721100205.D9eIJIvrouRfqDeSgq19qzQUzm0t45-5_FZ7bctmegw@z \
    --to=husio@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 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 NNTP newsgroup(s).