Revert ASAN detect_stack_use_after_return for #2431 repro

The option did not detect the bug in CI -- the resolver worker write
likely lands on the heap (via the gaicb's pai pointer) or happens after
the test process exits, neither of which stack-use-after-return can
catch. Roll back to relying on the job-level timeout: bug present ->
post-cleanup hangs ~8min then job-level timeout cancels at 10min total;
bug fixed -> job completes in ~2min.
This commit is contained in:
yhirose
2026-04-28 09:40:12 +09:00
parent 49708a18b2
commit 69d3998453

View File

@@ -164,13 +164,7 @@ jobs:
run: |
cd test
ARCH=$(uname -m)
# detect_stack_use_after_return=1 is the direct detector for this
# bug: when the resolver worker writes back to the destroyed
# stack-local gaicb, ASAN aborts immediately with a stack trace
# naming getaddrinfo_with_timeout. Without it the bug only shows
# up as an orphan-process hang at job teardown.
CPPHTTPLIB_TEST_ISSUE_2431=1 \
ASAN_OPTIONS=detect_stack_use_after_return=1 \
LSAN_OPTIONS=suppressions=lsan_suppressions.txt \
setarch "$ARCH" -R \
./test --gtest_filter='GetAddrInfoAsyncCancelTest.*'