Reverse the direction of the stack dump, so prints the most recent call last, instead of first. This matches the behavior of Haxe errors.

Alternatively, if you would prefer it to remain in the current order, perhaps the error could be printed first, and then the stack trace? One of these approaches should help make it clear what happened right before the error was thrown

git-svn-id: http://hxcpp.googlecode.com/svn/trunk@679 d391954c-4287-11de-baa7-5503b21fc9cb
Reverting previous change, but moving the "Critical Error" message before the stack dump to make the output more consistent with common error messages

git-svn-id: http://hxcpp.googlecode.com/svn/trunk@680 d391954c-4287-11de-baa7-5503b21fc9cb