error: cannot open output file
-
@Axel-Spoerl Sorry, missed the little drop-down arrows! Seems I already have the debug info.
@nekkceb
No worries. I am curious to learn what you observe! -
@nekkceb
No worries. I am curious to learn what you observe!@Axel-Spoerl Well, I apologize, but I am not expert in debugging compiler issues. I cant see how to do a breakpoint as you suggest, I tried stepping into the .exec function, but that did not do anything. Looks like I am going to have to live with this rather bizarre new behavior or rely on someone more expert to figure it out!
-
@nekkceb
No worries. I am curious to learn what you observe!@Axel-Spoerl I found a solution that works much better than re-booting the computer between each debug cycle. Turns out opening a cmd-prompt, cd to the directory with the offending .exe file and just enter
del <filename>.exe /fdoes the trick!
However, I still wonder why this behavior started all of a sudden about a week ago, no recent updates to either Windows or Qt. I probably fat-fingered a setting somewhere in Qt, but have not been able to find it so far. -
@Axel-Spoerl I found a solution that works much better than re-booting the computer between each debug cycle. Turns out opening a cmd-prompt, cd to the directory with the offending .exe file and just enter
del <filename>.exe /fdoes the trick!
However, I still wonder why this behavior started all of a sudden about a week ago, no recent updates to either Windows or Qt. I probably fat-fingered a setting somewhere in Qt, but have not been able to find it so far.@nekkceb
Does it require you use the/foption? If so, that forces deleting of read-only file, which (unlike Linux) Windows/cmddoes not allow you to do directly, it requires you make it non-read-only first. If the file being created is somehow being marked read-only then it would not surprise me that Creator or whatever does not do this and expects to open the file directly.How that relates to the
.exeyou are producing I do not know, nor why it has just started happening. But see whether the file is read-only and/or you have to usedel /fto delete it, that's a clue.BTW, do you use a virus scanner? It is possible that is looking at generated
.exefiles, worth switching it off or telling it to ignore the build directory. -
@nekkceb
Does it require you use the/foption? If so, that forces deleting of read-only file, which (unlike Linux) Windows/cmddoes not allow you to do directly, it requires you make it non-read-only first. If the file being created is somehow being marked read-only then it would not surprise me that Creator or whatever does not do this and expects to open the file directly.How that relates to the
.exeyou are producing I do not know, nor why it has just started happening. But see whether the file is read-only and/or you have to usedel /fto delete it, that's a clue.BTW, do you use a virus scanner? It is possible that is looking at generated
.exefiles, worth switching it off or telling it to ignore the build directory.@JonB Thanks for the ideas. Turns out the /f option is not needed. But things are certainly strange! If I try to delete the file in the Windows File Explorer, I get this message:
Note I tried to do this after stopping the program in the debugger AND closing QtCreator. The file is NOT marked as read-only, though windows thinks it is 'open' somehow. Using the cmd-prompt, just issue adel BIPSMain.exedeletes it and allows me to rebuild it in QtCreator. -
@JonB Thanks for the ideas. Turns out the /f option is not needed. But things are certainly strange! If I try to delete the file in the Windows File Explorer, I get this message:
Note I tried to do this after stopping the program in the debugger AND closing QtCreator. The file is NOT marked as read-only, though windows thinks it is 'open' somehow. Using the cmd-prompt, just issue adel BIPSMain.exedeletes it and allows me to rebuild it in QtCreator.@nekkceb
Is BIPS20 your project / BIPSMain.exe your executable?
If so: It's in use bygdbor however the MinGW derivate is called. -
@JonB Thanks for the ideas. Turns out the /f option is not needed. But things are certainly strange! If I try to delete the file in the Windows File Explorer, I get this message:
Note I tried to do this after stopping the program in the debugger AND closing QtCreator. The file is NOT marked as read-only, though windows thinks it is 'open' somehow. Using the cmd-prompt, just issue adel BIPSMain.exedeletes it and allows me to rebuild it in QtCreator.@nekkceb said in error: cannot open output file:
del BIPSMain.exedeletes it and allows me to rebuild it in QtCreator.(Now that we know
/f/read-only is not the issue.) Then you are fortunate. Clearly something has it open in some shape or form, in which case Windows does not normally allow to delete the file. So this is surprising but convenient.If you really are sure tasklist/taskman cannot find the executable file still running, and you still want to know what is going on, you could download whatever currently works for Windows which allows you to view open handles in the OS. There used to be a procman and/or procexplorer (or similar names) from sysinternals for this, if they don't work I imagine there are alternatives now.
-
@nekkceb
Is BIPS20 your project / BIPSMain.exe your executable?
If so: It's in use bygdbor however the MinGW derivate is called.@Axel-Spoerl Agree, you have mentioned that before, but neither BIPSMain nor gdb are found in the Task Manager, or (per @JonB suggestion) the procexp64.exe from sysinternals. Both do appear in the TaskManager when the debug session is running, but both go away when the application exits. So, I am truly at a loss, but knowing I can just delete BIPSMain use the del command in a DOS-box helps a lot.
-
@Axel-Spoerl Agree, you have mentioned that before, but neither BIPSMain nor gdb are found in the Task Manager, or (per @JonB suggestion) the procexp64.exe from sysinternals. Both do appear in the TaskManager when the debug session is running, but both go away when the application exits. So, I am truly at a loss, but knowing I can just delete BIPSMain use the del command in a DOS-box helps a lot.
@nekkceb
If you have got procexp64 or similar working, instead of look for executable running it has something which lets you pick a file and find all "open handles" into it. That really ought finddynamicspline.exewith a handle!Or, from error message
:-1: error: cannot open output file dynamicspline.exe: Invalid argument.
the
invalid argumentmight just indicate that the file "does not exist" or "half exists", is in a funny state so that it cannot be overwritten but can be deleted.... Anyway, that's me out of suggestions now. -
After running my code in debug mode, stop the process and make changes, when I try to rebuild or re-run in the debugger I get this compiler error:
:-1: error: cannot open output file dynamicspline.exe: Invalid argument.
There is an old post related to this, but in that case, it seems they could find the process still running in the task manager. My application is a windows GUI, not a console application, and I do not see any processes related to it in the task manager that I can kill. The only thing that works for me is to exit QTCreator, then find the build directory (e.g. build-dynamicspline-Desktop_Qt_6_2_8_MinGW_64_bit-Debug) and rename it to something like 'jumk'.. I can then re-start Qt-Creator, re-buiuld and ruyn again. But this is a pain to deal with. AND it just started, i was working fine a few days ago!
Windows 10, latest build, Qt Creator 11.0.0, compiling with Desktop Qt 6.2.8 MinGW 64-bit -
N nekkceb has marked this topic as solved on
