Eric Blake wrote:
> Do we want to try and make test-c-stack.sh a bit smarter to avoid core
> dumps on more platforms, when we are gracefully handling an
> intentional stack overflow? Or at a minimum try to clean up any core
> files that may be created as a side effect of the test running
> successfully?
Done through this patch:
2025-04-14 Bruno Haible <br...@clisp.org>
c-stack tests: Remove left-over core dump file.
Suggested by Eric Blake in
<https://lists.gnu.org/archive/html/bug-gnulib/2025-04/msg00101.html>.
* tests/test-c-stack2.sh: Remove 'core' and 'test-c-stack.core' when
done.
diff --git a/tests/test-c-stack2.sh b/tests/test-c-stack2.sh
index b7f8b26bd9..7d62de1bc9 100755
--- a/tests/test-c-stack2.sh
+++ b/tests/test-c-stack2.sh
@@ -4,6 +4,10 @@ tmpfiles=""
trap 'rm -fr $tmpfiles' HUP INT QUIT TERM
tmpfiles="t-c-stack2.tmp"
+# Prepare to clean up a core dump file, assuming the most common naming
+# conventions for such files. (Core dump file names may be customized
+# through /proc/sys/kernel/core_pattern or 'coredumpctl'.)
+tmpfiles="$tmpfiles core test-c-stack.core"
# Sanitize exit status within a subshell, since some shells fail to
# redirect stderr on their message about death due to signal.
