- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi folks, I've got a strange one here:
I'm using Win7/VC++ 2008/ Intel C++ compiler 11 plug-in.
I have a project that was working correctly. It runs well, produces the correct output and I can debug it if need be. I thought I'd make some modifications to the class layout and - being cautious - copied the whole project into another folder and started modifying this duplicate version. When I tried to run in debug mode and stop at a breakpoint, to my astonishment the debugger stopped in a function that I wasn't calling. I double-checked that I was indeed building in debug mode and tried again...same behavior. After fussing for an hour or so (which included several restarts of both the computer and VS 2008) I decided to go back to the original unmodified project that was working properly and try that again. Incredibly, this one now behaves the same when debugging even though on Friday everything was working normally and it hadn't been modified since then (other than being copied). When I run the debug version without actually trying to debug it i.e. no breakpoints, etc it runs all the way through and generates the correct output as usual. When trying to run to a breakpoint or the cursor, it stops in sections of the code that it shouldn't be in in the first place and starts hopping around, landing on blank lines, etc. After a lot of head-scratching - > swearing, I've noticed the following pattern which implies there's some sort of graphical error in what is being shown in my code editor window when trying to debug. Consider two functions in my source code, arranged one above the other:
void Func1(int x)
{
if(x == 0) // <- Put a breakpoint at this conditional statement. At runtime this evaluates to false and it will test the next condition.
{
.
.
}
else if(x == 1)
{
.
.
}
}
void Func2(int y)
{
// Some general code, completely unrelated to the code above.
.
.
. // <- When debugging, debugger stops here (call it "line x") even though this code/function is never invoked!
.
.
.
.
. // <- It then jumps here, as though it were executing the "if-else" block in the above function, which I believe it is since it runs fine.
.
}
It seems like the code block being shown in the code editor while I'm trying to step through under the debugger is not the code block that is actually being interrogated by the debugger. This explains the crazy behavior as I try to step through line by line. One other note...if I try to interrogate the value of a variable by hovering the mouse cursor over it, I get nothing. If I add the variable to the watch window I get an error in the watch window warning me the variable is not in the stack frame, or something like that. Has anyone else seen this? Is my project somehow schmutzed-up and, if so, is there a way to force a total "regeneration" to try and get things back to normal? Thanks in advance!
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It makes me wonder if any Windows update during the weekend caused such problem.
Please read this KB - http://software.intel.com/en-us/articles/debugger-console-windows-do-not-close-when-exiting-debugger-and-visual-studio/
The symptom is different though.
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
"error C2719: 'm1': formal parameter with __declspec(align('32')) won't be aligned" in the Intel file "immintrin.h"
It's because the include-dir list have the icl-include in front of vc-include. When building with vc, you need the immintrin.h from vc-include.
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try following:
1. instead of set the compiler to VC from project property dialog; use menu "Project -> Intel C++ Compiler -> Use Visual C++" to set the project or solution to use VC
2. but above may not solve the compile-error problem if you have specified the IntelC-include in the project property or the tools -> option -> project & solutions -> VC build directories. Otherwise the step #1 should solve the compile-time error.
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
were you able to build with VC before?
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can you search your code to see how "immintrin.h" is included? and check this file's compile option (properties to see if it has /I option to include IntelC's include dir).
The "xmmintrin.h" is also offered by VC as well. In order to use the "xmmintrin.h", you need to add "/I C:\Program Files (x86)\Intel\Compiler\11.1\065\include\ia32".
(**** Are you still using 11.1.038 pkg? if so, please upgrade to 11.1.065 (update 6). There is a bug in 11.1.038 that may cause programs to hang on Windows 7 - http://software.intel.com/en-us/articles/program-crashes-or-hangs-on-some-systems/. )
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, let's find out why the code doesn't compile with VC.
On the file that you get the compilation error about "immintrin.h", please turn-on "Show Includes" under the file's property -> C/C++ -> Advanced. Then "Compile" this file, in theoutput window, you'll see a list of .h files including the full path.
Check where the "emmintrin.h" and "xmmintrin.h" are coming from. It should display the "immintrin.h" with a full path as well.
From the output, you might be able to figure out why the .h are coming from those different dir. Or you can save the output to a txt file, and attach to your response.
Thanks,
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I know.
But still, try the "Show Include" for the file that you get the error C2719, and send me the buildlog.htm.
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The buildlog does help.
1. to build with "CL", either under the file's property or project property, there are "Additional include directories" set as "C:\Program Files (x86)\Intel\Compiler\11.1\038\IPP\ia32\Include;C:\Program Files (x86)\Intel\Compiler\11.1\038\include". You need to remove it.
If your code use IPP, you can keep the IPP include dir, but remove the IntelC include dir.
2. About the "error #10032: argument is too long....", it seems the IDE integration does know how to pass the above concatenated directories. You just need to use "edit" to add multiple include dirs and then it should work. like the screen capture below:
Let me know how it goes.
Thanks,
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jennifer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page