Executable fails when mingw bin directory added to PATH
After having a good msys2 mingw64 environment for several weeks I made an insignificant change to my code and stopped my entire graphical app from displaying any output.
After playing around for several hours I copied the executable and all required DLLs to a clean directory and executed the app from there. It works fine!
If I launch the app from a cmd like so, it works:
C:appfolder>set PATH=%PATH%;.dlls
C:appfolder>.ovcc.exe
If I launch the app from a cmd like so, it doesn't work:
C:appfolder>set PATH=%PATH%;C:msys64mingw64bin
C:appfolder>.ovcc.exe
There are no errors or crashes and I can cleanly (blindly) exit the app. It just stopped displaying anything!!!
Now all the dlls in the appfolder have being directly copied from the C:msys64mingw64bin folder. So they should be the same!
It has also stopped displaying anything when envoked from a msys terminal (which naturally has C:msys64mingw64bin in the PATH).
So what have I broken in my mingw environment?
gcc shared-libraries mingw
edited Jan 1 at 17:24
Joey Mallone
1,84231628
asked Dec 31 '18 at 8:05
user2715390user2715390
186
add a comment |
After having a good msys2 mingw64 environment for several weeks I made an insignificant change to my code and stopped my entire graphical app from displaying any output.
After playing around for several hours I copied the executable and all required DLLs to a clean directory and executed the app from there. It works fine!
If I launch the app from a cmd like so, it works:
C:appfolder>set PATH=%PATH%;.dlls
C:appfolder>.ovcc.exe
If I launch the app from a cmd like so, it doesn't work:
C:appfolder>set PATH=%PATH%;C:msys64mingw64bin
C:appfolder>.ovcc.exe
There are no errors or crashes and I can cleanly (blindly) exit the app. It just stopped displaying anything!!!
Now all the dlls in the appfolder have being directly copied from the C:msys64mingw64bin folder. So they should be the same!
It has also stopped displaying anything when envoked from a msys terminal (which naturally has C:msys64mingw64bin in the PATH).
So what have I broken in my mingw environment?
gcc shared-libraries mingw
edited Jan 1 at 17:24
Joey Mallone
1,84231628
asked Dec 31 '18 at 8:05
user2715390user2715390
186
Could you share more about the insignificant change? Reverting it doesn't fix the issue? you could download Dependency Walker and check your executable.
– CristiFati
Jan 4 at 16:55
Disregard I found the real issue.
– user2715390
Jan 6 at 6:25
add a comment |
After having a good msys2 mingw64 environment for several weeks I made an insignificant change to my code and stopped my entire graphical app from displaying any output.
After playing around for several hours I copied the executable and all required DLLs to a clean directory and executed the app from there. It works fine!
If I launch the app from a cmd like so, it works:
C:appfolder>set PATH=%PATH%;.dlls
C:appfolder>.ovcc.exe
If I launch the app from a cmd like so, it doesn't work:
C:appfolder>set PATH=%PATH%;C:msys64mingw64bin
C:appfolder>.ovcc.exe
There are no errors or crashes and I can cleanly (blindly) exit the app. It just stopped displaying anything!!!
Now all the dlls in the appfolder have being directly copied from the C:msys64mingw64bin folder. So they should be the same!
It has also stopped displaying anything when envoked from a msys terminal (which naturally has C:msys64mingw64bin in the PATH).
So what have I broken in my mingw environment?
gcc shared-libraries mingw
edited Jan 1 at 17:24
Joey Mallone
1,84231628
asked Dec 31 '18 at 8:05
user2715390user2715390
186
After having a good msys2 mingw64 environment for several weeks I made an insignificant change to my code and stopped my entire graphical app from displaying any output.
After playing around for several hours I copied the executable and all required DLLs to a clean directory and executed the app from there. It works fine!
If I launch the app from a cmd like so, it works:
C:appfolder>set PATH=%PATH%;.dlls
C:appfolder>.ovcc.exe
If I launch the app from a cmd like so, it doesn't work:
C:appfolder>set PATH=%PATH%;C:msys64mingw64bin
C:appfolder>.ovcc.exe
There are no errors or crashes and I can cleanly (blindly) exit the app. It just stopped displaying anything!!!
Now all the dlls in the appfolder have being directly copied from the C:msys64mingw64bin folder. So they should be the same!
It has also stopped displaying anything when envoked from a msys terminal (which naturally has C:msys64mingw64bin in the PATH).
So what have I broken in my mingw environment?
gcc shared-libraries mingw
gcc shared-libraries mingw
edited Jan 1 at 17:24
Joey Mallone
1,84231628
asked Dec 31 '18 at 8:05
user2715390user2715390
186
edited Jan 1 at 17:24
Joey Mallone
1,84231628
asked Dec 31 '18 at 8:05
user2715390user2715390
186
edited Jan 1 at 17:24
Joey Mallone
1,84231628
edited Jan 1 at 17:24
Joey Mallone
1,84231628
edited Jan 1 at 17:24
Joey Mallone
1,84231628
1,84231628
asked Dec 31 '18 at 8:05
user2715390user2715390
186
asked Dec 31 '18 at 8:05
user2715390user2715390
186
asked Dec 31 '18 at 8:05
user2715390user2715390
186
186
Could you share more about the insignificant change? Reverting it doesn't fix the issue? you could download Dependency Walker and check your executable.
– CristiFati
Jan 4 at 16:55
Disregard I found the real issue.
– user2715390
Jan 6 at 6:25
add a comment |
Could you share more about the insignificant change? Reverting it doesn't fix the issue? you could download Dependency Walker and check your executable.
– CristiFati
Jan 4 at 16:55
Disregard I found the real issue.
– user2715390
Jan 6 at 6:25
Could you share more about the insignificant change? Reverting it doesn't fix the issue? you could download Dependency Walker and check your executable.
– CristiFati
Jan 4 at 16:55
Could you share more about the insignificant change? Reverting it doesn't fix the issue? you could download Dependency Walker and check your executable.
– CristiFati
Jan 4 at 16:55
Disregard I found the real issue.
– user2715390
Jan 6 at 6:25
Disregard I found the real issue.
– user2715390
Jan 6 at 6:25
add a comment |
1 Answer
1
active
oldest
votes
My insignificant change had a roll on effect.
I changed :
int main(int argc, char **argv)
to
int main(int argc, char *argv)
Which I thought shouldn't make any difference.
But that was enough that the configuration files for the app could not be properly processed and default (bad) values were written back to those files.
Even though I changed the code back the conf files were now damaged and subsequent runs were just reading bad conf files.
The bad conf files contained a parameter to skip frames which was now set to zero giving me the blank screen.
Once I replaced the conf files it worked either way!!!
PATH was not the issue!!!
edited Jan 6 at 10:58
CristiFati
13.2k72436
answered Jan 6 at 6:34
user2715390user2715390
186
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53985067%2fexecutable-fails-when-mingw-bin-directory-added-to-path%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
My insignificant change had a roll on effect.
I changed :
int main(int argc, char **argv)
to
int main(int argc, char *argv)
Which I thought shouldn't make any difference.
But that was enough that the configuration files for the app could not be properly processed and default (bad) values were written back to those files.
Even though I changed the code back the conf files were now damaged and subsequent runs were just reading bad conf files.
The bad conf files contained a parameter to skip frames which was now set to zero giving me the blank screen.
Once I replaced the conf files it worked either way!!!
PATH was not the issue!!!
edited Jan 6 at 10:58
CristiFati
13.2k72436
answered Jan 6 at 6:34
user2715390user2715390
186
add a comment |
My insignificant change had a roll on effect.
I changed :
int main(int argc, char **argv)
to
int main(int argc, char *argv)
Which I thought shouldn't make any difference.
But that was enough that the configuration files for the app could not be properly processed and default (bad) values were written back to those files.
Even though I changed the code back the conf files were now damaged and subsequent runs were just reading bad conf files.
The bad conf files contained a parameter to skip frames which was now set to zero giving me the blank screen.
Once I replaced the conf files it worked either way!!!
PATH was not the issue!!!
edited Jan 6 at 10:58
CristiFati
13.2k72436
answered Jan 6 at 6:34
user2715390user2715390
186
add a comment |
My insignificant change had a roll on effect.
I changed :
int main(int argc, char **argv)
to
int main(int argc, char *argv)
Which I thought shouldn't make any difference.
But that was enough that the configuration files for the app could not be properly processed and default (bad) values were written back to those files.
Even though I changed the code back the conf files were now damaged and subsequent runs were just reading bad conf files.
The bad conf files contained a parameter to skip frames which was now set to zero giving me the blank screen.
Once I replaced the conf files it worked either way!!!
PATH was not the issue!!!
edited Jan 6 at 10:58
CristiFati
13.2k72436
answered Jan 6 at 6:34
user2715390user2715390
186
My insignificant change had a roll on effect.
I changed :
int main(int argc, char **argv)
to
int main(int argc, char *argv)
Which I thought shouldn't make any difference.
But that was enough that the configuration files for the app could not be properly processed and default (bad) values were written back to those files.
Even though I changed the code back the conf files were now damaged and subsequent runs were just reading bad conf files.
The bad conf files contained a parameter to skip frames which was now set to zero giving me the blank screen.
Once I replaced the conf files it worked either way!!!
PATH was not the issue!!!
edited Jan 6 at 10:58
CristiFati
13.2k72436
answered Jan 6 at 6:34
user2715390user2715390
186
edited Jan 6 at 10:58
CristiFati
13.2k72436
edited Jan 6 at 10:58
CristiFati
13.2k72436
edited Jan 6 at 10:58
CristiFati
13.2k72436
13.2k72436
answered Jan 6 at 6:34
user2715390user2715390
186
answered Jan 6 at 6:34
user2715390user2715390
186
answered Jan 6 at 6:34
user2715390user2715390
186
186
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53985067%2fexecutable-fails-when-mingw-bin-directory-added-to-path%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could you share more about the insignificant change? Reverting it doesn't fix the issue? you could download Dependency Walker and check your executable.
– CristiFati
Jan 4 at 16:55
Disregard I found the real issue.
– user2715390
Jan 6 at 6:25