- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
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
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
- Balises:
- Intel® Fortran Compiler
Lien copié
12 Réponses
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
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?
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?
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Quoting - bmchenry
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?
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?
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
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.
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Quoting - Steve Lionel (Intel)
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.
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
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?
If you copy the solution folder to another location and open it there, can you build and run it?
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
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?
If you copy the solution folder to another location and open it there, can you build and run it?
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
I see nothing of consequence in the .vfproj. Is there also a .vfproj.yourname.user file?
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Nothing interesting there either. Sorry, out of ideas.
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
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
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
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
Same thing for Configuration Properties->Linker.
Set to the actual output file (directory/path/name)
that should get things up and running in debug
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Quoting - jimdempseyatthecove
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
Répondre
Options du sujet
- S'abonner au fil RSS
- Marquer le sujet comme nouveau
- Marquer le sujet comme lu
- Placer ce Sujet en tête de liste pour l'utilisateur actuel
- Marquer
- S'abonner
- Page imprimable