From 280cb724b7499ed4f09f9a54e5ae457b1eb254ae Mon Sep 17 00:00:00 2001 From: qunyanm Date: Wed, 25 Nov 2015 11:50:43 -0800 Subject: Use the EndCurly token when creating the ReturnCmd for unifiedExit When there are more than one exit blocks, an unified exit block is created which includes a ReturnCmd. However, the ReturnCmd is created with NoToken. This causes the line/column number reported for a failed postcondition to be (0,0). The right token should be the EndCurly since the ReturnCmd is in the exit block. --- Test/test2/BadLineNumber.bpl.expect | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 Test/test2/BadLineNumber.bpl.expect (limited to 'Test/test2/BadLineNumber.bpl.expect') diff --git a/Test/test2/BadLineNumber.bpl.expect b/Test/test2/BadLineNumber.bpl.expect new file mode 100644 index 00000000..bc5d1984 --- /dev/null +++ b/Test/test2/BadLineNumber.bpl.expect @@ -0,0 +1,7 @@ +BadLineNumber.bpl(15,1): Error BP5003: A postcondition might not hold on this return path. +BadLineNumber.bpl(5,3): Related location: This is the postcondition that might not hold. +Execution trace: + BadLineNumber.bpl(9,5): anon0 + BadLineNumber.bpl(14,5): anon3_Else + +Boogie program verifier finished with 0 verified, 1 error -- cgit v1.2.3