Ricardo Wurmus <[email protected]> skribis:
> Oddly, I cannot seem to get a core dump, even after setting ulimit -c
> unlimited. Is there a way to run the failing builder manually?
No.
Could you try something like this:
diff --git a/test-env.in b/test-env.in
index f66a0db..9cdd479 100644
--- a/test-env.in
+++ b/test-env.in
@@ -90,7 +90,8 @@ then
--substitute-urls="$GUIX_BINARY_SUBSTITUTE_URL" &
daemon_pid=$!
- trap "kill $daemon_pid ; rm -rf $NIX_STATE_DIR" EXIT
+ echo "please attach gdb to $daemon_pid and hit enter"
+ read
fi
# Avoid issues that could stem from l10n, such as language/encoding
When you see the message, run this from another terminal:
$ gdb
(gdb) attach 1234
(gdb) set detach-on-fork off
(gdb) continue
Normally GDB will stop when the child process receives SIGSEGV. At that
point, you should be able to type “bt” to get the backtrace.
Could you try that?
Thanks in advance,
Ludo’.
