- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are spawning the DF command from within a (C++) program to compile Fortran code. The code used to spawn DF is CreateProcess within C++, and we have an abortHandler to kill the created process.
This works well, until the user aborts the DF process. The DF process does abort, but the DECFOR90.EXE process continues. Some of our compilation times are long, and we must have an easy way of killing this process too.
As it is possible for the user to have more than one compilation running on the same machine, is there a way of aborting the correct DECFOR90.EXE process?
This works well, until the user aborts the DF process. The DF process does abort, but the DECFOR90.EXE process continues. Some of our compilation times are long, and we must have an easy way of killing this process too.
As it is possible for the user to have more than one compilation running on the same machine, is there a way of aborting the correct DECFOR90.EXE process?
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can't think of a way to do this, but an alternative is for you to spawn DECFOR90.EXE directly. You'll need to figure out what switches and arguments to pass - the easiest way to do that is to issue a sample DF command with the /watch switch included - the driver will then display the complete invocation of DECFOR90.EXE.
Steve
Steve

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