From: "godlygeek at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/30272] Unwinding multithreaded musl applications fails
Date: Sun, 02 Apr 2023 23:42:41 +0000 [thread overview]
Message-ID: <bug-30272-10460-smprQ2U4vL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30272-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30272
--- Comment #1 from Matt Wozniski <godlygeek at gmail dot com> ---
I encountered this issue using `dwfl_getthread_frames`, and I've found that
calling `dwfl_frame_reg` to check if the stack pointer register was the same
for two frames in a row and breaking out if so seems to work around it. I'm not
sure if that's entirely correct, though. Are there any legitimate cases where
two different frames passed to the callback would have the same stack pointer?
My impression is that the stack pointer should change for every function call
because the return address is stored on the stack, but perhaps there are some
architectures where that isn't the case...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-02 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 23:39 [Bug libdw/30272] New: " godlygeek at gmail dot com
2023-04-02 23:42 ` godlygeek at gmail dot com [this message]
2023-04-03 5:44 ` [Bug libdw/30272] " sam at gentoo dot org
2023-04-06 22:16 ` mark at klomp dot org
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=bug-30272-10460-smprQ2U4vL@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).