From: Plut0nio <Plut0nio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: MISSING INFO: Crash: Dolphin musl can't paste a file.
Date: Mon, 05 Aug 2024 17:02:50 +0200 [thread overview]
Message-ID: <20240805150250.8E3BB28651@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51303@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2429 bytes --]
New comment by Plut0nio on void-packages repository
https://github.com/void-linux/void-packages/issues/51303#issuecomment-2269292679
Comment:
> you can prove it's a stack overflow with like
>
> ```
> # crashing frame
> (lldb) f 0
> # note down the 0x address
> (lldb) reg read $sp
> # frame that the thread starts at (__clone)
> (lldb) f 7
> # note it again
> (lldb) reg read $sp
> ```
>
> then in python
>
> ```
> 0xsecondone - 0xfirstone
> ```
>
> gives you a value larger than 128KiB, so the stack has overflowed. the -Wl link args i posted would fix it
`f 7` gave me `error: Frame index (7) out of range.`, so I had to use `f 1` instead. Here's my output:
```
$ lldb dolphin
(lldb) target create "dolphin"
Current executable set to '/usr/bin/dolphin' (x86_64).
(lldb) run
Process 23321 launched: '/usr/bin/dolphin' (x86_64)
Process 23321 stopped
* thread #11, name = 'KIO::WorkerThre', stop reason = signal SIGSEGV: invalid permissions for mapped object (fault address: 0x7fffe05b13a8)
frame #0: 0x00007fffe0ab4eb9
-> 0x7fffe0ab4eb9: orq $0x0, (%rsp)
0x7fffe0ab4ebe: cmpq %r11, %rsp
0x7fffe0ab4ec1: jne 0x7fffe0ab4eb2
0x7fffe0ab4ec3: subq $0x2c8, %rsp ; imm = 0x2C8
(lldb) f 0
frame #0: 0x00007fffe0ab4eb9
-> 0x7fffe0ab4eb9: orq $0x0, (%rsp)
0x7fffe0ab4ebe: cmpq %r11, %rsp
0x7fffe0ab4ec1: jne 0x7fffe0ab4eb2
0x7fffe0ab4ec3: subq $0x2c8, %rsp ; imm = 0x2C8
(lldb) reg read $sp
rsp = 0x00007fffe05b13a8
(lldb) f 7
error: Frame index (7) out of range.
(lldb) f 1
frame #1: 0x00007fffe05d2520
-> 0x7fffe05d2520: movabsb -0x4fffffaaaaa9c8c5, %al
0x7fffe05d2529: cmpl (%rdi), %esi
0x7fffe05d252b: pushq %rsi
0x7fffe05d252c: pushq %rbp
(lldb) f 2
error: Frame index (2) out of range.
(lldb) f 1
frame #1: 0x00007fffe05d2520
-> 0x7fffe05d2520: movabsb -0x4fffffaaaaa9c8c5, %al
0x7fffe05d2529: cmpl (%rdi), %esi
0x7fffe05d252b: pushq %rsi
0x7fffe05d252c: pushq %rbp
(lldb) reg read $sp
rsp = 0x00007fffe05d23f8
```
According to Python, 0x00007fffe05d23f8 - 0x00007fffe05b13a8 = 135248, which is indeed greater than 128 kibibytes (131072 bytes).
I have no idea how to use those `-Wl,-z,stack-size=0x200000`, though. Is that for linking/building? All my KDE stuff (except for kio-admin) was downloaded and installed from the Void repos.
next prev parent reply other threads:[~2024-08-05 15:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 2:43 [ISSUE] Dolphin musl can't paste a file (Segmentation fault) hervyqa
2024-07-19 7:56 ` sgn
2024-07-19 7:59 ` sgn
2024-07-19 8:08 ` sgn
2024-07-19 23:03 ` hervyqa
2024-07-21 1:49 ` sgn
2024-07-31 16:07 ` MISSING INFO: Crash: Dolphin musl can't paste a file nekopsykose
2024-08-05 13:52 ` Plut0nio
2024-08-05 14:06 ` nekopsykose
2024-08-05 15:02 ` Plut0nio [this message]
2024-08-05 15:08 ` nekopsykose
2024-08-05 16:21 ` Plut0nio
2024-08-06 14:35 ` Plut0nio
2024-08-06 18:44 ` nekopsykose
2024-08-06 19:29 ` Plut0nio
2024-08-06 19:31 ` nekopsykose
2024-08-06 20:03 ` Plut0nio
2024-08-06 20:07 ` nekopsykose
2024-08-06 20:07 ` nekopsykose
2024-08-06 20:07 ` nekopsykose
2024-08-06 20:13 ` Plut0nio
2024-08-06 20:15 ` nekopsykose
2024-08-06 20:15 ` nekopsykose
2024-08-06 21:10 ` Plut0nio
2024-08-07 6:16 ` hervyqa
2024-08-07 6:16 ` hervyqa
2024-08-13 4:55 ` [ISSUE] [CLOSED] " classabbyamp
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=20240805150250.8E3BB28651@inbox.vuxu.org \
--to=plut0nio@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).