* Re: telegram-desktop-4.14.2 segfault on start
2024-01-03 21:38 [ISSUE] telegram-desktop-4.14.2 segfault on start dm17
@ 2024-01-03 21:52 ` classabbyamp
2024-01-03 21:53 ` Johnnynator
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2024-01-03 21:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48056#issuecomment-1876019174
Comment:
what's the full backtrace (`bt`) from glibc?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: telegram-desktop-4.14.2 segfault on start
2024-01-03 21:38 [ISSUE] telegram-desktop-4.14.2 segfault on start dm17
2024-01-03 21:52 ` classabbyamp
@ 2024-01-03 21:53 ` Johnnynator
2024-01-03 21:53 ` classabbyamp
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Johnnynator @ 2024-01-03 21:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 258 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/48056#issuecomment-1876019475
Comment:
Can you get the full backtrace. (type `backtrace` in gdb after it crashed)
Also what is your timezone set to?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: telegram-desktop-4.14.2 segfault on start
2024-01-03 21:38 [ISSUE] telegram-desktop-4.14.2 segfault on start dm17
2024-01-03 21:52 ` classabbyamp
2024-01-03 21:53 ` Johnnynator
@ 2024-01-03 21:53 ` classabbyamp
2024-01-03 21:59 ` dm17
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2024-01-03 21:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48056#issuecomment-1876019174
Comment:
what's the full backtrace (`bt`) from gdb?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: telegram-desktop-4.14.2 segfault on start
2024-01-03 21:38 [ISSUE] telegram-desktop-4.14.2 segfault on start dm17
` (2 preceding siblings ...)
2024-01-03 21:53 ` classabbyamp
@ 2024-01-03 21:59 ` dm17
2024-01-03 22:55 ` Johnnynator
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: dm17 @ 2024-01-03 21:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
New comment by dm17 on void-packages repository
https://github.com/void-linux/void-packages/issues/48056#issuecomment-1876026268
Comment:
`date +%Z` > CST
```(gdb) backtrace
#0 0x00007ffff7fbb98c in scan_trans (alt=<synthetic pointer>, local=1, t=-9223372014364800) at src/time/__tz.c:280
#1 __secs_to_zone (t=t@entry=-9223372014364800, local=local@entry=1, isdst=isdst@entry=0x7fffffffd8b0, offset=offset@entry=0x7fffffffd8b8,
oppoff=oppoff@entry=0x7fffffffd888, zonename=zonename@entry=0x7fffffffd8c0) at src/time/__tz.c:355
#2 0x00007ffff7fbc328 in mktime (tm=0x7fffffffd940) at src/time/mktime.c:10
#3 0x00007ffff2d256c8 in qMkTime(tm*) () from /lib/libQt6Core.so.6
#4 0x00007ffff2e73b0a in ?? () from /lib/libQt6Core.so.6
#5 0x00007ffff2e6a433 in ?? () from /lib/libQt6Core.so.6
#6 0x00007ffff2e6bda5 in QDateTime::setMSecsSinceEpoch(long long) () from /lib/libQt6Core.so.6
#7 0x00007ffff2e6cbc3 in QDateTime::fromMSecsSinceEpoch(long long, QTimeZone const&) () from /lib/libQt6Core.so.6
#8 0x00007ffff2e6cedf in QDateTime::currentDateTime(QTimeZone const&) () from /lib/libQt6Core.so.6
#9 0x00007ffff2e6cf2c in QDateTime::currentDateTime() () from /lib/libQt6Core.so.6
#10 0x00005555582a015d in _logsEntryStart () at /builddir/telegram-desktop-4.14.2/Telegram/SourceFiles/logs.cpp:68
#11 0x00005555582a0b87 in Logs::writeDebug (v=...) at /builddir/telegram-desktop-4.14.2/Telegram/SourceFiles/logs.cpp:515
#12 0x00005555582a0f53 in Logs::writeMain (v=...) at /builddir/telegram-desktop-4.14.2/Telegram/SourceFiles/logs.cpp:511
#13 0x000055555704f15b in Core::Launcher::prepareSettings (this=this@entry=0x7ff4eec53690)
at /builddir/telegram-desktop-4.14.2/Telegram/SourceFiles/core/launcher.cpp:471
#14 0x000055555704f2c1 in Core::Launcher::init (this=0x7ff4eec53690)
at /builddir/telegram-desktop-4.14.2/Telegram/SourceFiles/core/launcher.cpp:317
#15 0x0000555557051574 in Core::Launcher::exec (this=0x7ff4eec53690)
at /builddir/telegram-desktop-4.14.2/Telegram/SourceFiles/core/launcher.cpp:354
#16 0x0000555555e9b124 in main (argc=<optimized out>, argv=<optimized out>) at /builddir/telegram-desktop-4.14.2/Telegram/SourceFiles/main.cpp:12
(gdb)```
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: telegram-desktop-4.14.2 segfault on start
2024-01-03 21:38 [ISSUE] telegram-desktop-4.14.2 segfault on start dm17
` (3 preceding siblings ...)
2024-01-03 21:59 ` dm17
@ 2024-01-03 22:55 ` Johnnynator
2024-01-07 12:10 ` [ISSUE] [CLOSED] " Johnnynator
2024-01-07 12:10 ` Johnnynator
6 siblings, 0 replies; 8+ messages in thread
From: Johnnynator @ 2024-01-03 22:55 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/48056#issuecomment-1876080579
Comment:
https://git.musl-libc.org/cgit/musl/commit/?id=3b7b4155570b4b9054465785be2992c92cb7d7b1
The backtrace (trying to access `index[-1]` and segfaulting) reads like this triggers a bug in musl which might be fixed with the linked commit.
But I could not reproduce the crash yet.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [ISSUE] [CLOSED] telegram-desktop-4.14.2 segfault on start
2024-01-03 21:38 [ISSUE] telegram-desktop-4.14.2 segfault on start dm17
` (4 preceding siblings ...)
2024-01-03 22:55 ` Johnnynator
@ 2024-01-07 12:10 ` Johnnynator
2024-01-07 12:10 ` Johnnynator
6 siblings, 0 replies; 8+ messages in thread
From: Johnnynator @ 2024-01-07 12:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Closed issue by dm17 on void-packages repository
https://github.com/void-linux/void-packages/issues/48056
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.9_1 x86_64-musl GenuineIntel uptodate rFFFFF
### Package(s) Affected
telegram-desktop
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
running telegram-desktop runs the application as it has without fail for as long as I can remember
### Actual behaviour
running telegram-desktop immediately segfaults
### Steps to reproduce
I've installed telegram-desktop-dbg as well, and I see the following with gdb:
1) run `gdb telegram-desktop`
2) type `run` -> `Starting program: /usr/bin/telegram-desktop`
3) see debug output:
```Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7fbb98c in scan_trans (alt=<synthetic pointer>, local=1, t=-9223372014364800) at src/time/__tz.c:280
warning: 280 src/time/__tz.c: No such file or directory```
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: telegram-desktop-4.14.2 segfault on start
2024-01-03 21:38 [ISSUE] telegram-desktop-4.14.2 segfault on start dm17
` (5 preceding siblings ...)
2024-01-07 12:10 ` [ISSUE] [CLOSED] " Johnnynator
@ 2024-01-07 12:10 ` Johnnynator
6 siblings, 0 replies; 8+ messages in thread
From: Johnnynator @ 2024-01-07 12:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 188 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/48056#issuecomment-1880041209
Comment:
a394e150af7d40075e74bc8dfc361706246c4529
^ permalink raw reply [flat|nested] 8+ messages in thread