From: Guinevere Larsen <guinevere@redhat.com>
To: "Schimpe, Christina" <christina.schimpe@intel.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 01/12] gdb, testsuite: Rename set_sanitizer_default to append_environment.
Date: Tue, 28 Jan 2025 10:45:22 -0300 [thread overview]
Message-ID: <798ec44e-0dc5-4dff-a26f-c8b331b981f6@redhat.com> (raw)
In-Reply-To: <20241220200501.324191-2-christina.schimpe@intel.com>
On 12/20/24 5:04 PM, Schimpe, Christina wrote:
> The procedure set_sanitizer_default has been used for the configuration
> of ASAN specific environment variables. However, it is actually a
> generic function. Rename it to append_environment so that its purpose
> is more clear.
I think this is a good change, but in that case we should also rename
set_sanitizer_1 and set_sanitizer. I think the conversion should be:
set_sanitizer -> append_environment
set_sanitizer_1 -> append_environment_1
set_sanitizer_default -> append_environment_default
Also, I can see that patch 12 (and maybe others) use the
append_environment call. If the user had already set GLIBC_TUNABLES, the
test wouldn't update the value if I understand the TCL code correctly.
Is that the expected outcome? If not, I would suggest the alternative of
renaming set_sanitizer_1 to append_environment, so that set_sanitizer*
can continue to work as is, and you can manually set the environment
variables in a more obvious way.
--
Cheers,
Guinevere Larsen
She/Her/Hers
> ---
> gdb/testsuite/gdb.base/libsegfault.exp | 2 +-
> gdb/testsuite/gdb.threads/attach-slow-waitpid.exp | 2 +-
> gdb/testsuite/lib/gdb.exp | 8 ++++----
> 3 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.base/libsegfault.exp b/gdb/testsuite/gdb.base/libsegfault.exp
> index 2c16fe8932a..fb62bdb8746 100644
> --- a/gdb/testsuite/gdb.base/libsegfault.exp
> +++ b/gdb/testsuite/gdb.base/libsegfault.exp
> @@ -42,7 +42,7 @@ proc gdb_spawn_with_ld_preload {lib cmdline_opts} {
> # ASan runtime does not come first in initial library list; you should
> # either link runtime to your application or manually preload it with
> # LD_PRELOAD.
> - set_sanitizer_default ASAN_OPTIONS verify_asan_link_order 0
> + append_environment ASAN_OPTIONS verify_asan_link_order 0
>
> gdb_spawn_with_cmdline_opts $cmdline_opts
> }
> diff --git a/gdb/testsuite/gdb.threads/attach-slow-waitpid.exp b/gdb/testsuite/gdb.threads/attach-slow-waitpid.exp
> index 28d70daad8c..abe8d434558 100644
> --- a/gdb/testsuite/gdb.threads/attach-slow-waitpid.exp
> +++ b/gdb/testsuite/gdb.threads/attach-slow-waitpid.exp
> @@ -83,7 +83,7 @@ proc gdb_spawn_with_ld_preload {lib} {
> # ASan runtime does not come first in initial library list; you should
> # either link runtime to your application or manually preload it with
> # LD_PRELOAD.
> - set_sanitizer_default ASAN_OPTIONS verify_asan_link_order 0
> + append_environment ASAN_OPTIONS verify_asan_link_order 0
>
> gdb_start
> }
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 7ee2043f0f8..a86f534528c 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -76,11 +76,11 @@ proc set_sanitizer { env_var var_id val } {
>
> # Add VAR_ID=VAL to ENV_VAR, unless ENV_VAR already contains a VAR_ID setting.
>
> -proc set_sanitizer_default { env_var var_id val } {
> +proc append_environment { env_var var_id val } {
> set_sanitizer_1 $env_var $var_id $val 1
> }
>
> -set_sanitizer_default TSAN_OPTIONS suppressions \
> +append_environment TSAN_OPTIONS suppressions \
> $srcdir/../tsan-suppressions.txt
>
> # When using ThreadSanitizer we may run into the case that a race is detected,
> @@ -89,14 +89,14 @@ set_sanitizer_default TSAN_OPTIONS suppressions \
> # Try to prevent this by setting history_size to the maximum (7) by default.
> # See also the ThreadSanitizer docs (
> # https://github.com/google/sanitizers/wiki/ThreadSanitizerFlags ).
> -set_sanitizer_default TSAN_OPTIONS history_size 7
> +append_environment TSAN_OPTIONS history_size 7
>
> # If GDB is built with ASAN (and because there are leaks), it will output a
> # leak report when exiting as well as exit with a non-zero (failure) status.
> # This can affect tests that are sensitive to what GDB prints on stderr or its
> # exit status. Add `detect_leaks=0` to the ASAN_OPTIONS environment variable
> # (which will affect any spawned sub-process) to avoid this.
> -set_sanitizer_default ASAN_OPTIONS detect_leaks 0
> +append_environment ASAN_OPTIONS detect_leaks 0
>
> # List of procs to run in gdb_finish.
> set gdb_finish_hooks [list]
next prev parent reply other threads:[~2025-01-28 13:48 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 20:04 [PATCH 00/12] Add CET shadow stack support Schimpe, Christina
2024-12-20 20:04 ` [PATCH 01/12] gdb, testsuite: Rename set_sanitizer_default to append_environment Schimpe, Christina
2025-01-28 13:45 ` Guinevere Larsen [this message]
2025-01-30 13:07 ` Schimpe, Christina
2025-01-30 14:27 ` Tom de Vries
2025-01-30 16:39 ` Schimpe, Christina
2024-12-20 20:04 ` [PATCH 02/12] gdbserver: Add optional runtime register set type Schimpe, Christina
2025-01-28 13:35 ` Guinevere Larsen
2025-01-30 10:28 ` Schimpe, Christina
2025-01-30 13:53 ` Guinevere Larsen
2025-01-30 17:43 ` Schimpe, Christina
2025-02-06 2:59 ` Thiago Jung Bauermann
2025-02-06 12:15 ` Schimpe, Christina
2024-12-20 20:04 ` [PATCH 03/12] gdbserver: Add assert in x86_linux_read_description Schimpe, Christina
2025-02-06 3:00 ` Thiago Jung Bauermann
2024-12-20 20:04 ` [PATCH 04/12] gdb: Sync up x86-gcc-cpuid.h with cpuid.h from gcc 14 branch Schimpe, Christina
2025-02-06 3:03 ` Thiago Jung Bauermann
2025-02-06 12:23 ` Schimpe, Christina
2024-12-20 20:04 ` [PATCH 05/12] gdb, gdbserver: Use xstate_bv for target description creation on x86 Schimpe, Christina
2025-01-30 14:51 ` Guinevere Larsen
2025-01-30 16:45 ` Schimpe, Christina
2025-02-06 3:09 ` Thiago Jung Bauermann
2025-02-06 12:33 ` Schimpe, Christina
2024-12-20 20:04 ` [PATCH 06/12] gdb, gdbserver: Add support of Intel shadow stack pointer register Schimpe, Christina
2025-02-06 3:13 ` Thiago Jung Bauermann
2025-02-06 14:33 ` Schimpe, Christina
2025-02-08 3:44 ` Thiago Jung Bauermann
2024-12-20 20:04 ` [PATCH 07/12] gdb, bfd: amd64 linux coredump support with shadow stack Schimpe, Christina
2025-02-06 3:15 ` Thiago Jung Bauermann
2025-02-07 11:54 ` Schimpe, Christina
2024-12-20 20:04 ` [PATCH 08/12] gdb: Handle shadow stack pointer register unwinding for amd64 linux Schimpe, Christina
2025-01-30 14:29 ` Guinevere Larsen
2025-01-30 16:11 ` Schimpe, Christina
2025-01-30 16:13 ` Guinevere Larsen
2025-01-30 16:40 ` Schimpe, Christina
2025-02-06 3:30 ` Thiago Jung Bauermann
2025-02-06 14:40 ` Schimpe, Christina
2024-12-20 20:04 ` [PATCH 09/12] gdb, gdbarch: Enable inferior calls for shadow stack support Schimpe, Christina
2025-02-06 3:31 ` Thiago Jung Bauermann
2025-02-06 15:07 ` Schimpe, Christina
2025-02-08 3:57 ` Thiago Jung Bauermann
2025-02-10 8:37 ` Schimpe, Christina
2024-12-20 20:04 ` [PATCH 10/12] gdb: Implement amd64 linux shadow stack support for inferior calls Schimpe, Christina
2025-02-06 3:34 ` Thiago Jung Bauermann
2025-02-07 11:55 ` Schimpe, Christina
2024-12-20 20:05 ` [PATCH 11/12] gdb, gdbarch: Introduce gdbarch method to get the shadow stack pointer Schimpe, Christina
2025-01-28 20:27 ` Guinevere Larsen
2025-01-30 10:33 ` Luis Machado
2025-01-30 12:34 ` Schimpe, Christina
2025-01-30 13:42 ` Guinevere Larsen
2025-02-06 3:35 ` Thiago Jung Bauermann
2025-02-07 12:01 ` Schimpe, Christina
2025-02-08 4:03 ` Thiago Jung Bauermann
2025-02-10 8:58 ` Schimpe, Christina
2025-02-11 1:53 ` Thiago Jung Bauermann
2025-02-15 3:45 ` Thiago Jung Bauermann
2025-02-16 10:45 ` Schimpe, Christina
2025-02-20 8:48 ` Schimpe, Christina
2025-02-21 5:10 ` Thiago Jung Bauermann
2025-02-21 9:41 ` Schimpe, Christina
2024-12-20 20:05 ` [PATCH 12/12] gdb: Enable displaced stepping with shadow stack on amd64 linux Schimpe, Christina
2024-12-20 20:14 ` Eli Zaretskii
2025-01-02 9:04 ` Schimpe, Christina
2025-01-02 9:15 ` Eli Zaretskii
2025-02-06 3:37 ` Thiago Jung Bauermann
2025-01-16 14:01 ` [PING][PATCH 00/12] Add CET shadow stack support Schimpe, Christina
2025-01-27 9:44 ` [PING*2][PATCH " Schimpe, Christina
2025-01-30 15:01 ` [PATCH " Guinevere Larsen
2025-01-30 17:46 ` Schimpe, Christina
2025-02-04 3:57 ` Thiago Jung Bauermann
2025-02-04 9:40 ` Schimpe, Christina
2025-02-06 3:44 ` Thiago Jung Bauermann
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=798ec44e-0dc5-4dff-a26f-c8b331b981f6@redhat.com \
--to=guinevere@redhat.com \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@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