Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28446 Discussions

Annoying popup "Intel Parallel Debugger Extension"

Andrew_Smith
New Contributor III
554 Views
Using latest IVF in VS2008, each time I detach from my EXE (non fortran exe with Fortran dll) I get a message popup saying:

Runtime-load events have been detected but the corresponding load-notifications are partially or fully missing. Make sure that in the main menu under Debug > Exceptions > Win32 Exceptions, alll three "Intel Parallel Debugger Extension Exception" entries have a tickmark in the "Thrown" column, the re-run your application.

I did what it said but thrown is ticked for all three.

What does the message mean and how can I get it to go away?
0 Kudos
7 Replies
Steven_L_Intel1
Employee
554 Views
I asked a debugger specialist to help you. It may be a day or two.
0 Kudos
Stefan_
Beginner
554 Views
Is there a fix to this problem? I'm getting the same error message using Intel C++ Compiler XE 12.0 Update 1 and Visual Studio 2010 on Windows 7. Thanks a lot.
0 Kudos
Steven_L_Intel1
Employee
554 Views
Please follow the instructions in the compiler release notes for configuring the Parallel Debugger Extension in Visual Studio.
0 Kudos
Stefan_
Beginner
554 Views
Ich checked the Release notes for Intel C++ Composer XE for Windows from this link http://software.intel.com/en-us/articles/intel-c-composer-xe-2011-release-notes/
both for "RTM Release Notes" and "Release Notes - Update 1". There's no information which might be related to this problem.

I'm neither using the Intel Compiler nor the Intel Parallel Debugger Extension, i.e. nothing is enabled, but still this error message is showing up.
0 Kudos
Steven_L_Intel1
Employee
554 Views
You must have installed one of the Intel compilers or else you would not see this message. The instructions I referenced are in section 7.2 of the Intel C++ release notes. I repeat them here for your reference.

If you are using Microsoft Visual Studio 2005, there are six Intel-specific exceptions that
must be enabled manually. Select Debug > Exceptions, expand the Win32
Exceptions tree, and enable items:
a1a01db0 Intel Parallel Debugger Extension Exception 0
a1a01db1 Intel Parallel Debugger Extension Exception 1
a1a01db2 Intel Parallel Debugger Extension Exception 2
a1a01db3 Intel Parallel Debugger Extension Exception 3
a1a01db4 Intel Parallel Debugger Extension Exception 4
a1a01db5 Intel Parallel Debugger Extension Exception 5
This needs to be done once per project.

Let me know if this solves the problem. You can also, if you desire, do a "change" on the Intel compiler product you have installed and set the Parallel Debugger Extension to "Will not be installed". This will remove it.
0 Kudos
Stefan_
Beginner
554 Views
Thank you Steve for your support. I'm using Visual Studio 2010 so I thought this wouldn't apply.

If I do this in Visual Studio 2010: Select Debug > Exceptions, expand the Win32 Exceptions tree

There're no exceptions like these:
a1a01db0 Intel Parallel Debugger Extension Exception 0
a1a01db1 Intel Parallel Debugger Extension Exception 1
a1a01db2 Intel Parallel Debugger Extension Exception 2
a1a01db3 Intel Parallel Debugger Extension Exception 3
a1a01db4 Intel Parallel Debugger Extension Exception 4
a1a01db5 Intel Parallel Debugger Extension Exception 5


If I do Debug > Start Debugging and then go to Debug > Exceptions > Win32 Exceptions the above exceptions are listed there. All exceptions are enabled (i.e. they're all checked in the column "Throw" and they're all checked in the column "User-unhandled")

If I then do Debug > Stop Debugging then the said popup shows up.

But: it is not repeatable.
0 Kudos
Stefan_
Beginner
554 Views
The problem is repeatable:

1. Start Visual Studio 2010
2. Open my project
3. Debug > Start Debugging
4. Debug > Stop Debugging
5. Error message

If I do Start and Stop Debugging again there's no error message anymore. Between Start and Stop Debugging I checked Debug > Exceptions > Win32 Exceptions to make sure that all exceptions are enabled.
0 Kudos
Reply