From 834b8ae4f4854ca2b935829d56c390279459dced Mon Sep 17 00:00:00 2001
From: Hans-Peter Deifel <hpd@hpdeifel.de>
Date: Mon, 12 Dec 2016 16:20:00 +0100
Subject: [PATCH] search: Don't compare vertices solely on their next syscall

This was mistakenly done for the next-vertex set of our graph. While
it sounds like a serious bug, in practice it doesn't seem to affect
output so much for our examples. Probably because it doesn't happen
often that two different states execute the same syscall (but it could
happen).
---
 src/Search/Search.hs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Search/Search.hs b/src/Search/Search.hs
index 4b1b64d..e173e24 100644
--- a/src/Search/Search.hs
+++ b/src/Search/Search.hs
@@ -31,7 +31,7 @@ data Vertex = Vertex
   }
 
 instance Eq Vertex where
-  Vertex x meta1 == Vertex y meta2 = (x, metaSyscall meta1) == (x, metaSyscall meta2)
+  Vertex x meta1 == Vertex y meta2 = (x, metaSyscall meta1) == (y, metaSyscall meta2)
 
 instance Ord Vertex where
   compare (Vertex x meta1) (Vertex y meta2) = compare (x, metaSyscall meta1) (y, metaSyscall meta2)
-- 
GitLab