specsharp Issue Tracker Rss Feed

Created Issue: website link for z3 on the home page should be updated [10114]

cl1motorsports — Tue, 29 Jan 2013 21:12:13 GMT

z3 has been moved to codeplex, the new uri is http://z3.codeplex.com/

Commented Issue: VS2010 gets very slow [10113]

mueller — Thu, 29 Mar 2012 15:36:22 GMT

Ok, I decided to try Spec# and created a test project, the problem is that anything I do in VS2010 takes seconds to accomplish, like editing project properties, compiling, etc. I am not sure if that is how it's supposed to be. Is there any way to fight this problem?

Thanks!
Comments: Dear anonymous Spec# user, I have not experienced such a slow-down. I am also using Spec# in VS2010, and the performance is just fine. Do you see the slow-down even when you turn off the verifier or when you are not editing/compiling the program? Do you see it only when you are working on a Spec# project or did the installation slow down VS for other languages as well? Peter

Created Issue: VS2010 gets very slow [10113]

middlewest — Fri, 23 Mar 2012 14:35:28 GMT

Commented Issue: Does not work with VS2010 Ultimate [10112]

wuestholz — Thu, 22 Dec 2011 06:39:14 GMT

I'm using Visual Studio 2010 Ultimate and the Spec# Plugin does not work for me - installing it the described way using the Binaries does not change anything. Obviously, I'm not the only one with the problem (see comment in the Binary installation description).
Comments: Since I don't have VS 2010 Ultimate, I would be glad if you could be a bit more specific about what exactly doesn't work. (The comment that you refer to is from before we added support for VS 2010.)

Created Issue: Does not work with VS2010 Ultimate [10112]

rindPHI — Wed, 21 Dec 2011 10:10:33 GMT

Closed Issue: internal error: 2 typechecking errors detected [10111]

wuestholz — Sat, 03 Dec 2011 17:09:59 GMT

SpecSharp version 2011-10-03
Visual Studio 2010 Professional

On attach SpecSharp says "internal error: 2 typechecking errors detected" on "using System;"

Closed Issue: internal error: 2 typechecking errors detected [10111]

wuestholz — Sat, 03 Dec 2011 17:09:59 GMT

SpecSharp version 2011-10-03
Visual Studio 2010 Professional

On attach SpecSharp says "internal error: 2 typechecking errors detected" on "using System;"

Edited Issue: internal error: 2 typechecking errors detected [10111]

wuestholz — Thu, 24 Nov 2011 16:15:08 GMT

SpecSharp version 2011-10-03
Visual Studio 2010 Professional

On attach SpecSharp says "internal error: 2 typechecking errors detected" on "using System;"

Commented Issue: internal error: 2 typechecking errors detected [10111]

wuestholz — Thu, 24 Nov 2011 16:14:29 GMT

SpecSharp version 2011-10-03
Visual Studio 2010 Professional

On attach SpecSharp says "internal error: 2 typechecking errors detected" on "using System;"
Comments: This has been fixed in change set b797fa8ecf66.

Created Issue: internal error: 2 typechecking errors detected [10111]

kornevgen — Tue, 25 Oct 2011 13:14:33 GMT

SpecSharp version 2011-10-03
Visual Studio 2010 Professional

On attach SpecSharp says "internal error: 2 typechecking errors detected" on "using System;"

Closed Issue: Unused local variable crashes PeWriter initialization. [6552]

wuestholz — Thu, 13 Oct 2011 19:36:46 GMT

The following input throws an exception in Metadata\Sources\PeWriter.cs in PeWriter.Initialize()

class Example {
public static void Foo() { int i; int j = 0; }
}

Giving an initial value for "i" makes the throw go away.
i and j both make it into "currentScope", but only j is in localDefIndex.

Closed Issue: Project creation wizard does not copy the templates (Visual Studio 2010) [10110]

wuestholz — Thu, 13 Oct 2011 19:36:28 GMT

When a new project is created, the project creation wizard references the templates (e.g., Class1.ssc, AssemblyInfo.ssc) instead of copying them to the new project directory. The same happens if new classes are added.

This works correctly under Visual Studio 2008, but not under Visual Studio 2010.

(originally reported by robimalik)

This has been fixed in change set 45c103fb3936.

Closed Issue: Spec# Checkin tests fail on 64bit Windows 7 [8334]

wuestholz — Thu, 13 Oct 2011 19:35:13 GMT

When run on a 64bit Windows 7 the Spec# Checkin test suite (Microsoft.SpecSharp\Checkin Tests\Runtests.bat) fails with over 50 unexpected errors, whereas it runs as expected on Windows XP.

Strangely, most of the errors are about not implementing interface members of System.Collections, although the reported classes do implement these interfaces (and compile successfully on 32bit Windows XP).

I uploaded a summary of the errors to http://n.ethz.ch/~scmalte/aste/checkintests.html, the document also contains a link to the suite output.
Comments: Apparently all tests pass if you force ssc to run in 32-bit mode using the CorFlags.exe utility.

Edited Issue: Project creation wizard does not copy the templates (Visual Studio 2010) [10110]

wuestholz — Fri, 29 Apr 2011 05:15:37 GMT

Created Issue: Project creation wizard does not copy the templates (Visual Studio 2010) [10110]

wuestholz — Tue, 26 Apr 2011 19:53:21 GMT

Closed Issue: ?? does not compile correctly [5356]

alexanderjsummers — Sat, 05 Mar 2011 11:48:00 GMT

The ?? operator, inherited from C# and with the meaning "return the left-hand operand unless it is null; if it is null, return the right-hand operator", is not compiled correctly by the Spec# compiler. In particular, I found that (s.Tok.filename ?? ".dfy") compiles the str2 in:

string str;
string str2;
if (str == null)
{
str2 = ".dfy";
}
else
{
str2 = str;
}

Note that "str" is uninitialized. It should have been initialized to the left-hand operand of ??.
Comments:

Commented Issue: ?? does not compile correctly [5356]

alexanderjsummers — Sat, 05 Mar 2011 11:47:51 GMT

Fixed in revision 63112. The bug happened when the first operator was neither a local variable nor a parameter.

Created Issue: Unnecessary trace positions for the 'pack' operation of an 'expose' block [10109]

wuestholz — Tue, 11 Jan 2011 10:03:37 GMT

Due to the way the trace position filtering currently works, we get unnecessary trace positions for the 'pack' operation of an 'expose' block. In principle, we should never get trace positions for 'pack' operations.

Created Issue: SscBoogie crashes when it is run on .Net 4.0 dll [9789]

wuestholz — Fri, 05 Nov 2010 13:29:47 GMT

When I run SscBoogie on a .Net 4.0 dll (e.g. Core.dll from Boogie) it throws an AssumeException.

The following command can be used to reproduce the crash:
sscboogie /noVerify Core.dll

Commented Issue: min/max causes nullpointer exception [9016]

rustanleino — Mon, 09 Aug 2010 23:46:01 GMT

The following code results in a Nullreference Exception when built with Visual Studio 2008.
<p>
I'm not sure whether this syntax of min and max is supported as I have seen some examples only.
Comments: ** Comment from web user: rustanleino **

This is a bug. It seems that the combination of "old" with min/max causes the compiler to crash.

Beyond that, it seems there's also a second bug, which is that the type of min/max comes out as "int", even when the operands are "long" as in this case.

As a workaround, you can write:

ensures 0 < amount ==> _value == (old(_value) + amount < _max_value ? old(_value) + amount : _max_value);
ensures amount <= 0 ==> _value == (old(_value) + amount < 0 ? 0 : old(_value) + amount);

or the more verbose:

ensures 0 < amount ==>
_value <= old(_value) + amount && _value <= _max_value &&
(_value == old(_value) + amount || _value == _max_value);
ensures amount <= 0 ==>
old(_value) + amount <= _value && 0 <= _value &&
(_value == old(_value) + amount || _value == 0);

Also, the body of the "increase" method is not correct.