[prev in list] [next in list] [prev in thread] [next in thread]
List: binutils
Subject: [PATCH 5/5] ld/doc: use "stack trace" instead of "unwind" for SFrame
From: Indu Bhagat via Binutils <binutils () sourceware ! org>
Date: 2023-01-31 23:34:29
Message-ID: 20230131233429.3708328-6-indu.bhagat () oracle ! com
[Download RAW message or body]
SFrame format is meant for generating stack traces only.
ld/
* ld.texi: Replace the use of "unwind" with "stack trace".
---
ld/ld.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ld/ld.texi b/ld/ld.texi
index db3a9f09b45..36005dc2b0d 100644
--- a/ld/ld.texi
+++ b/ld/ld.texi
@@ -2835,7 +2835,7 @@ section and ELF @code{PT_GNU_EH_FRAME} segment header.
Request creation of @code{.eh_frame} unwind info for linker
generated code sections like PLT. This option is on by default
if linker generated unwind info is supported. This option also
-controls the generation of @code{.sframe} unwind info for linker
+controls the generation of @code{.sframe} stack trace info for linker
generated code sections like PLT.
@kindex --enable-new-dtags
--
2.39.0
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic