topic Re: Start Debugging problem in Intel® Fortran Compiler

Start Debugging problem

gib — Tue, 01 Sep 2009 09:09:30 GMT

I'm using 11.0.072
I build the debug version of my program, and set the working directory and command arguments. If I then click the Start Without Debugging button, the program executes as expected. If I clich the Start Debugging button an error box pops up and tells me "Unable to start program 'D:\x\y\z\debug\fubar.exe'. The specified working directory does not exist or is not a full path." But the program path is precisely what executes without debugging. What could be wrong?

Thanks
Gib

Re: Start Debugging problem

bmchenry — Tue, 01 Sep 2009 15:30:52 GMT

i'm guessing a typo in the debug specification of path somewhere in the Debug configuration.
to quickly check:
open one instance of your project in MVS/IVF, set to Release, change size so takes up half screen.
Open another instance of your project in MVS/IVF, set to Debug, change size so takes up other half of screen.
then in each Proejct-Properites
you can then directly compare and cut/paste from Release -> Debug where needed
then close Release w/o save
save Debug and voila! should work like a charm?

Re: Start Debugging problem

gib — Tue, 01 Sep 2009 19:38:52 GMT

Quoting - bmchenry

I did cut and paste the path, and as I said, the path reported in the error message is the CORRECT path. This path works for Start Without Debugging not for Start Debugging. The error message is wrong.

Re: Start Debugging problem

Steven_L_Intel1 — Tue, 01 Sep 2009 19:44:21 GMT

Note that the "working directory" is not the same as the executable path. By default it's the project folder, or what you have set for this property on the Debugging page. However, if this is wrong I would expect "Start without debugging" to complain as well.

Re: Start Debugging problem

gib — Tue, 01 Sep 2009 20:21:03 GMT

Quoting - Steve Lionel (Intel)

Oh, right, I was mixing up the two things. But the fact remains that the working directory is set correctly, and indeed works for the Start Without Debugging case. Very odd.

Re: Start Debugging problem

Steven_L_Intel1 — Tue, 01 Sep 2009 20:29:28 GMT

Attach the .vfproj file to a reply here - let's have a look at it.

If you copy the solution folder to another location and open it there, can you build and run it?

Re: Start Debugging problem

gib — Tue, 01 Sep 2009 23:17:07 GMT

Quoting - Steve Lionel (Intel)

Attach the .vfproj file to a reply here - let's have a look at it.

If you copy the solution folder to another location and open it there, can you build and run it?

OK Steve, here's the .vproj file.

Re: Start Debugging problem

Steven_L_Intel1 — Tue, 01 Sep 2009 23:48:11 GMT

I see nothing of consequence in the .vfproj. Is there also a .vfproj.yourname.user file?

Re: Start Debugging problem

gib — Wed, 02 Sep 2009 00:11:51 GMT

Quoting - gib

OK Steve, here's the .vproj file.

Here's the vproj user file.

Re: Start Debugging problem

Steven_L_Intel1 — Wed, 02 Sep 2009 12:50:31 GMT

Nothing interesting there either. Sorry, out of ideas.

Re: Start Debugging problem

jimdempseyatthecove — Wed, 02 Sep 2009 15:18:42 GMT

Gib,

I have experienced a similar problem
for 'D:xyzdebugfubar.exe'
try explicitly setting the working directory to 'D:xyzdebug'
Be sure to include the drive letter.
(adjust path for actual path)
I've noticed if anthing is in the Working directory, it must have a drive letter in the path, relative paths don't (seldom) work.

Jim Dempsey

Re: Start Debugging problem

bmchenry — Wed, 02 Sep 2009 15:42:50 GMT

Per Jim, I also normallyset the command, command arguments & working directory inConfiguration Properties->Debugging to the target location rather than the $(TargetPath) and/or leave blank
Same thing for Configuration Properties->Linker.
Set to the actual output file (directory/path/name)
that should get things up and running in debug

Re: Start Debugging problem

gib — Wed, 02 Sep 2009 20:00:20 GMT

Quoting - jimdempseyatthecove

That's it! Adding "d:" to the path fixed it. Interesting ...