summaryrefslogtreecommitdiff
path: root/Test/commandline/multiple_procs_verify_one_request_twice.bpl
diff options
context:
space:
mode:
authorGravatar Dan Liew <daniel.liew@imperial.ac.uk>2015-06-28 02:19:12 +0100
committerGravatar Dan Liew <daniel.liew@imperial.ac.uk>2015-06-28 02:30:14 +0100
commit7f4e6b0fab58bb3028cd0f1734fc97b3feafefdf (patch)
tree3b8c5537990c5f0137cd218c7030fb1b2f4738e0 /Test/commandline/multiple_procs_verify_one_request_twice.bpl
parent9c307b9fe6443f43195fe47915d0b6c09ec20f8d (diff)
Fix issue #16 reported by @crazykt
Previously when Boogie was passed the ``-proc:<NAME>`` argument on the command line it would verify any procedure whose name contained ``<NAME>`` which doesn't seem like correct behaviour. Now Boogie only tries to verify a procedure only if its name matches ``<NAME>`` exactly. I've added several test cases to check Boogie behaves as expected.
Diffstat (limited to 'Test/commandline/multiple_procs_verify_one_request_twice.bpl')
-rw-r--r--Test/commandline/multiple_procs_verify_one_request_twice.bpl20
1 files changed, 20 insertions, 0 deletions
diff --git a/Test/commandline/multiple_procs_verify_one_request_twice.bpl b/Test/commandline/multiple_procs_verify_one_request_twice.bpl
new file mode 100644
index 00000000..fe9c44ba
--- /dev/null
+++ b/Test/commandline/multiple_procs_verify_one_request_twice.bpl
@@ -0,0 +1,20 @@
+// RUN: %boogie -proc:foo -proc:foo "%s" > "%t"
+// RUN: %OutputCheck --file-to-check %t %s
+// CHECK-L: Boogie program verifier finished with 1 verified, 0 errors
+
+// Although the command line requests two verify this procedure twice we should
+// only do try once.
+procedure foo()
+{
+ assume true;
+}
+
+procedure bar()
+{
+ assert false;
+}
+
+procedure baz()
+{
+ assert false;
+}