Note that there are some explanatory texts on larger screens.

plurals
  1. POProblem spawning application
    text
    copied!<p>Gosh, this is so weird, I don't know what to say. The short version is that I have a simulator app which I spawn from my application when the user asks me to. It recently stopped working, though I can run the simulator fine from the command line or Start menu. This could be due to moving to VS2010 or Windows 7 or something I didn't notice reviewing source control diffs.</p> <p>I have a second simulator which I try to spawn in the same fashion and it works fine.</p> <p>By default, I'm using Qt3's QProcess wrapper around CreateProcess for this purpose, but I get the same behavior using system, my own CreateProcess, and ShellExecute.</p> <p>ShellExecute of a cmd.exe "/c application params" does provide me with some more information however. I get the dialog </p> <blockquote> <p>"The program can't start because MSVCR80.dll is missing from your computer. Try reinstalling the program to fix this problem." </p> </blockquote> <p>Inconveniently, both the parent application and the second simulator use MSVCR80.dll.</p> <p>Upon copying MSVC*80.dll from g:\windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5 to the same directory as my executable, the error message changes to </p> <blockquote> <p>"Runtime Error!<br> Program: g:\path\to\app.exe<br> R6034<br> An application has made an attempt to load the C runtime library incorrectly.<br> Please contact the application's support team for more information.</p> </blockquote> <p>Followed by </p> <blockquote> <p>The application was unable to start correctly (0xc0000142). Click OK to close the application.</p> </blockquote> <p>And, once again, the application runs fine from the command line with those dlls in place.</p> <hr> <p>Update:</p> <p>I suspected perhaps it was environment related, so changed my ShellExecute mechanism to do cmd /c set &amp;&amp; app params. I set up a cmd.exe with those same params and my app is now crashing similarly. Will update when I figure out why :)</p> <p>It is MATLAB's component runtime tool that is modifying my process's PATH variable to bad effect. It is prepending its own dir full of dll's and wreaking havoc.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload