If you haven't seen Chad's excellent series on how to capture all the different ways a process can terminate on windows, I highly recommend the previous installments:
This is some advanced mojo. I think it's a huge lost opportunity to ship internet-enabled software but not have it report back on exactly what went wrong when it crashes.
"Let's only write performance intense parts in C++", and have the rest in an interpreted scripting language, where things like this (and more) come much cheaper?
5 comments
[ 5.0 ms ] story [ 31.7 ms ] threadhttp://aegisknight.org/2009/04/imvu-crash-reporting-plugging...
http://aegisknight.org/2009/03/crash-reporting-in-imvu-last-...
http://aegisknight.org/2009/02/reporting-crashes-in-imvu-c-c...
http://aegisknight.org/2009/02/reporting-crashes-in-imvu-cal...
This is some advanced mojo. I think it's a huge lost opportunity to ship internet-enabled software but not have it report back on exactly what went wrong when it crashes.
But all this is all moot for production code since there's Google Breakpad: http://code.google.com/p/google-breakpad/
Instead of "Let's get C++ easier to debug"
why not:
"Let's only write performance intense parts in C++", and have the rest in an interpreted scripting language, where things like this (and more) come much cheaper?