blob: 38afde2c73f4953dc11e075e581927019a86ca52 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
From 8815239fc4e9cc8bc60a2703a622c0f5280f36c2 Mon Sep 17 00:00:00 2001
From: Marvin Schmidt <marv@exherbo.org>
Date: Mon, 26 Sep 2016 08:11:21 +0200
Subject: [PATCH 2/2] tests: Remove coredump tests
Upstream: No, not a suitable solution. Improvement of tests is/was discussed at https://lists.nongnu.org/archive/html/libunwind-devel/2016-02/
msg00019.html
The coredump tests rely on the assumption that coredump files
are created in the current working directory. This assumption is
false when e.g. systemd-coredump is used.
---
tests/Makefile.am | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/tests/Makefile.am b/tests/Makefile.am
index 7287e7b..796df0c 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -66,17 +66,6 @@ if SUPPORT_CXX_EXCEPTIONS
check_PROGRAMS_cdep += Ltest-cxx-exceptions
endif
-if OS_LINUX
-if BUILD_COREDUMP
- check_SCRIPTS_cdep += run-coredump-unwind
- noinst_PROGRAMS_cdep += crasher test-coredump-unwind
-
-if HAVE_LZMA
- check_SCRIPTS_cdep += run-coredump-unwind-mdi
-endif # HAVE_LZMA
-endif # BUILD_COREDUMP
-endif # OS_LINUX
-
perf: perf-startup Gperf-simple Lperf-simple Lperf-trace
@echo "########## Basic performance of generic libunwind:"
@./Gperf-simple
--
2.13.1
|
