summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2016-12-17 15:30:49 (GMT)
committerBoris Kolpackov <boris@codesynthesis.com>2016-12-17 15:30:49 (GMT)
commit3a33d1ccbc093e3bc6b27b565e4ca51ef072397a (patch)
tree17f3227c39ce6746827f882e6a2272ad4e9bca32
parent74e8166863bc390483d75bf2edaacec53a0b993d (diff)
Add feature: Print signal/core dump like shell/make
-rw-r--r--build2/test/testscript/list11
1 files changed, 11 insertions, 0 deletions
diff --git a/build2/test/testscript/list b/build2/test/testscript/list
index f25ccf2..6d6856c 100644
--- a/build2/test/testscript/list
+++ b/build2/test/testscript/list
@@ -11,3 +11,14 @@
later examination), print the error (including an info line with where is
the diff), and then (a fragment of) the diff. Theoretically, the .diff
can be large, so probably makes sense to limit it to a few KB?
+
+- Print signal/core dump like shell/make [feature karen]
+
+ Somehow bash and GNU make can detect which signal caused abnormal
+ termination and print it as well as whether core was dumped, for example:
+
+ Aborted (core dumped)
+ Segmentation fault
+
+ Would be nice to be just as smart plus, in case of a core, also print where
+ it is (normally terminated executable's working directory).