A.2.2. Cycles Checking; and add {16, “CYCLES_EXHAUSTED”}

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.
I believe the following tests require XFAIL to be set to YES…

A.2.2. Cycles Checking; and add {16, “CYCLES_EXHAUSTED”}

Original issue reported on code.google.com by boss...@yahoo.fr on 11 Jan 2013 at 3:53

[GoogleCodeExporter]

Note that is is also required to set XFAIL_YES.

Attached patch file corrects this.

I believe this change is a complete fix to the issue as the code reports *INFO: 
NACK_CYCLES_EXHAUSTED as shown below...

=== Testing A.2.2.  Cycles Checking ===

*INFO: NACK_CYCLES_EXHAUSTED
***ERROR: function: "tcomp_nackinfo_write()"
file: "c:\users\abc\documents\myboghe\doubango\branches\2.0\doubango\tinysigcomp
\src\tcomp_nackinfo.c"
line: "73"
MSG: Invalid parameter
***ERROR: function: "tcomp_udvm_runByteCode()"
file: "c:\users\abc\documents\myboghe\doubango\branches\2.0\doubango\tinysigcomp
\src\tcomp_udvm.c"
line: "485"
MSG: Execution failed for instruction = 20

==WE GOT A NACK

Expected failure: CYCLES_EXHAUSTED
=== A.2.2.  Cycles Checking STATUS: PASS ===

Original comment by alistair...@gmail.com on 15 Jan 2013 at 10:26

Attachments:

• test_tortures.h.patch

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 15 Jan 2013 at 6:05

• Changed state: NextRelease

[GoogleCodeExporter]

Fixed by r809

Original comment by boss...@yahoo.fr on 21 Jan 2013 at 8:50

• Changed state: Fixed