Is this Intel Compiler 10.1.013[IA32]'s SERIOUS BUG?

[liuchk]

I wrote the following test program in VS2005:

int main()
{
int x = 6;
for(int i = 0; i < 10; i++)
{
if(i > x)
{
continue;
}
}
return 0;
}

WhenI compile this test application in Debug modewith Intel compiler 10.1.013[IA32], I can't examineany variablevalue in Watch1 window. I get "CXX0069: Error: variable needs stack frame" message in value column. But, with MS compiler (VS 2005) , there is no such kind of problem.

Is this Intel Compiler 10.1.013[IA32]'s bug?

[liuchk]

P.S. : If the continue statement is commented, there will be no CXX0069 error message, variables value can be examined in Watch1 window properly even use Intel Compiler 10.1.013[IA32].

[liuchk]

With Intel compiler 10.1.011[IA-32], there is no such kind of problem.

[JenniferJ]

I can duplicate your problem. It looks like a bug to me. I'll create a bug report for it. When it's fixed, I'll post the pkg id here.

[Glenn_F_]

I've seen the same problem with 10.1.014[IA32] . Also, it was working with an earlier release. Does anyone know if this bug has been fixed?

[JenniferJ]

The bug is still open, but it's been worked on. I'll post a news here when the fix is available.

[Enrico_Z_]

Hi, are there any news ?

Now V10.1.021 is out, but I still cannot see any changes regarding this problem since the update to 10.1.014.

I'm working with some quite large projects under VS2005 and it makes me really unhappy to switch to the integrated VS-Compiler everytime I want to debug something, because in most parts of my libraries watching any variable is not possible.

Is there any workaround or build-setting to overcome this problem in the meantime ?

Best regards,

Enrico Zschau,
Lead Software Architect

SeeReal Technologies GmbH
www.seereal.com

[JenniferJ]

This bug doesn't seem so easy. During the fix, several other issues are discovered. It's still not fixed yet, but it's been actively worked on. If everything & testing goes well, it should be in the next 10.1 update.

[OLiet]

Hello,

having the same problem here. As a workaround, try declaring the variables as "static"

you wish to debug. It works for me.

Looking forward to an update soon.

Oliver

--

nanocosmos - multimedia software coding

http://www.nanocosmos.de

[JenniferJ]

Hello,

This bug has been fixed in our 10.1 branch. It should be in the next 10.1 beta update. (the pkg-id should be higher than 10.1.021).

[jackfrost]

Quoting - Jennifer Jiang (Intel)

Hello,

This bug has been fixed in our 10.1 branch. It should be in the next 10.1 beta update. (the pkg-id should be higher than 10.1.021).

I'm not sure,

It is realy fixed in 10.1.021 ???

I still have the same problem while debuging inintel 10.1.021

[jackfrost]

Quoting - jackfrost

Quoting - Jennifer Jiang (Intel)

Hello,

This bug has been fixed in our 10.1 branch. It should be in the next 10.1 beta update. (the pkg-id should be higher than 10.1.021).

I'm not sure,

It is realy fixed in 10.1.021 ???

I still have the same problem while debuging inintel 10.1.021

Sorry, i didnt see the word "higher" than 10.1.021)

So this problem is fixed in .025, but I still have some problems watching variables in MSVC2005:

"Expression Evaluator Error CXX0033 -The executable file did not have a valid OMF (Object Module Format) for debugging."

I've tried any complier keys: /Zi /Od /debug:full

with the same result.

[h_krishnan]

Interesting that such a simple code should cause a problem. I tried with MSVC 2005 SP 1 but did not notice any issue. to add