From 1f90406ac0cdb8ad04013e163b0fa0be336a36ee Mon Sep 17 00:00:00 2001 From: Martin Nowack Date: Thu, 19 Dec 2019 14:54:51 +0000 Subject: Assume assembly.ll is local to the run.istats file Assuming a `klee-out-*` directory is moved to a different path location, subsequent analysis of the run.istats with KCachegrind focusing on assembly is impossible as the `assembly.ll` cannot be found. The reason is that the absolute path of the object file (assembly.ll) is hard-coded as part of the generated run.istats. To fix this, assume that the file is local to the `run.istats`. --- test/Feature/SourceMapping.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/Feature/SourceMapping.c') diff --git a/test/Feature/SourceMapping.c b/test/Feature/SourceMapping.c index 30a9c2a8..6a071933 100644 --- a/test/Feature/SourceMapping.c +++ b/test/Feature/SourceMapping.c @@ -7,7 +7,7 @@ // RUN: FileCheck < %t.klee-out/run.istats %s // CHECK: positions: instr line -// CHECK: ob={{.*}}/SourceMapping.c{{.*}}/assembly.ll +// CHECK: ob=assembly.ll // Assuming the compiler doesn't reorder things, f0 should be first, and it // should immediately follow the first file name marker. -- cgit 1.4.1