"Nathan Mates" <nathan@visi.com> wrote in message
news:13cp4npfo5g1n73@corp.supernews.com...
In article <#Dwt22O5HHA.4476@TK2MSFTNGP06.phx.gbl>,
Arnie <NoOne@home.now> wrote:
If anyone knows of a tool that can help track this down I'd love to
hear about it. Also, if anyone would like more info, including some
code, please let me know.
Any serious app needs to have some sort of error logger that
includes a stack dump. There's plenty of samples online that show
this; one of those samples is:
http://www.codeguru.com/cpp/w-p/system/threading/print.php/c10317
You'll need to distribute stripped .pdb files with your apps for end
users to use it. Then, use SetUnhandledExceptionFilter() to set a
function that writes out a logfile with a callstack.
If it crashes after main exits, though, your exception handling
frames have already been cleaned up and you should already have
closed your logfile as well.
Try running it in Dependency Walker "Profiling" mode. Included free
in Windows SDK or as a free download at www.dependencywalker.com.
At least you should see what evil hook dlls are attaching to your
process.