Meaning of exit codes in my C++ MFC program
Posted on 2014-11-05
I am developing a dialog-based application in MFC using C++. I am using Visual Studio 2013. During debugging activities, I am used to seeing messages like "The thread 0x1648 has exited with code 20 (0x14)". Messages like this appear in the "Output" window of Visual Studio, after the program has terminated. I have poked around and come to believe that this exit code (20) is OK for a dialog based application. But today I see this message: "The thread 0x568 has exited with code 32812 (0x802c)." So I thought something went wrong.
But three things puzzle me. 1) There is no other indication that anything was wrong (no failures, exceptions, leaks, etc., reported). 2) I went back to a version of my program from a couple of weeks ago and it did the same thing. In fact I re-ran about a dozen versions stretching back a month and they all had the same exit code. This is really odd because they did not have that exit code at the time they were being developed and tested. 2) When I research exit codes, I started to wonder if it means anything at all. Apparently my application sets this code in some manner (I'm not doing it explicitly).
So, can you tell me if this means anything is wrong? Is there a way to determine what exit code 32812 means? Why does this sort of appear to be dependent not upon my application, but on my machine (i.e., the same program had an exit code of 20 a week ago).
Thanks very much for unraveling this mystery for me.