- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Link Copied
12 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see nothing of consequence in the .vfproj. Is there also a .vfproj.yourname.user file?
- 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
Nothing interesting there either. Sorry, out of ideas.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
![](/skins/images/9701FEC4E90D143B667C09F3DB2F340F/responsive_peak/images/icon_anonymous_message.png)
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page