From 1bd123bdf32c4a4e8930171c8e933f46debd177e Mon Sep 17 00:00:00 2001 From: Indu Bhagat Date: Thu, 2 Feb 2023 00:49:44 -0800 Subject: [PATCH] ld/doc: use "stack trace" instead of "unwind" for SFrame 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.30.2