Community
cancel
Showing results for 
Search instead for 
Did you mean: 
DarioMangoni
Beginner
143 Views

Debug directory within VS

Hi,
which is the directory in which Inspector runs the debugging session?
When I try to run Inspector with "Select analysis start location with debugger" it doesn't find some dlls that are in the same folder of the executable I'm trying to debug. (That are normally found when I debug normally).
I'm running Inspector from VS2015.

0 Kudos
5 Replies
DarioMangoni
Beginner
143 Views

Sorry, can't edit the post...
I already gave a look at the command line and it tells that:
-app-working-dir <path_where_exe_and_dlls_both_are>
so it seems to point to the correct folder (that is the same from which I run debug), but it doesn't find the dlls.
I tried also to insert that folder in PATH, but it doesn't work (also after rebooting MSVC)

Kevin_O_Intel1
Employee
143 Views

 

Does your Inspector an analysis work when not run under the debugger?

Inspector should use the -app-working-dir that you set

Kevin

DarioMangoni
Beginner
143 Views

Yes, it does!
Inspector is fully functional except when VS debugger comes into play.

I would say more:
I tried with a trivial example

int main()
{
	int c = 0;
	return c;
}

simply enough? and still I get
2016-09-16 12_18_47-serial_test - Microsoft Visual Studio (Administrator).png
no matter what are the other options: if I choose something involving the VS debugger I get this error.
I'm on VS2015 Enterprise Update 3 and Intel Parallel Studio XE 2016 Update3.

The command line is
inspxe-cl -collect mi2 -knob detect-uninit-read=true -knob revert-uninit=false -knob detect-leaks-on-exit=true -knob detect-resource-leaks=true -knob enable-memory-growth-detection=true -knob enable-on-demand-leak-detection=true -knob still-allocated-memory=true -knob stack-depth=16 -mrte-mode=auto -module-filter-mode=include -app-working-dir C:\workspace\serial_test_build -- C:\workspace\serial_test_build\Debug\serial_test.exe

Kevin_O_Intel1
Employee
143 Views

 

Understood. Let me check with our development team if this is a known issue.

What version of windows are you using?

Kevin

DarioMangoni
Beginner
143 Views

I'm on Win10. I tested Inspector both with the latest update 1607 of Win10 and with the previous one.
Both are affected by the same problem.

 

Reply