问题
My program is exitting with code '62097' (or in hex 0xF291). I know which DLL library is causing it, and I'm trying to figure out why it is messing up.
What does 62097 mean? How can I find out? I checked online, and as far as I can tell, generic Windows error codes don't go up to 62097.
Any other suggestions how I can go about debugging this problem? I use Dependency Walker on the DLL that's causing trouble, but everything is fine except missing IESHIMS.dll, IEFRAME.dll, and SHLWAPI.dll (which usually are missing when I use Dependency Walker).
The library in question is a 3rd party library that I compiled myself - it's quite possible I compiled it incorrectly - how can I tell if that's the case?
The program refuses to run before it enters main(), but only if I use a class imported from the DLL. If I'm not using anything from the DLL, the program starts fine.
The program is technically "running", but in the background, before the code ever reaches me. It's not a constructor of a class, because I tried doing something like this:
dllClass *class = new dllClass;
And the same thing occurred before execution reached the 'new', so it can't be a constructor with an infinite loop or something like that. It's running as a process, and is not "Not responding".
I'm using MinGW on Windows 7 32bit. What can I do to troubleshoot this? I appreciate any insight you can offer; meanwhile I'm trying to follow up a few more possible thoughts hoping I can narrow it down further.
回答1:
This library is made using Qt ? Because according to http://lists.qt-project.org/pipermail/development/2013-March/010157.html it the return code Qt uses when it kills a process.
来源：https://stackoverflow.com/questions/9187021/c-application-exit-error-code-62097-what-does-that-mean