This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/23004] New: unwind_stop doesn't work with alternate signal stack and shadow stack
- From: "hjl.tools at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 27 Mar 2018 02:12:21 +0000
- Subject: [Bug libc/23004] New: unwind_stop doesn't work with alternate signal stack and shadow stack
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=23004
Bug ID: 23004
Summary: unwind_stop doesn't work with alternate signal stack
and shadow stack
Product: glibc
Version: 2.28
URL: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85086
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: hjl.tools at gmail dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
When alternate signal stack is used with thread cancellation,
_Unwind_Resume fails when it tries to unwind shadow stack from signal
handler on alternate signal stack. The issue is that signal handler on
alternate signal stack uses a separate shadow stack and we must switch
to the original shadow stack to unwind it. But frame count will be wrong
in this case. For thread cancellation, there is no need to unwind shadow
stack since it will long jump back and exit.
--
You are receiving this mail because:
You are on the CC list for the bug.