getting a stack trace

[Eric Dean Tribble <tribble>]

If you just want a stack trace for your crashed program, and you don't
want to wait an hour, try adb!  

adb foo.exe
$c

then take the output (using cut and paste) and run it through the
c++filt2 program into a temporary file.  This will produce a readable
version of the call chain (in theory).  You don't get to see any
arguments, but you can tell where the crash happened.  This total
process took 5 minutes for the big executeable that Ravi generated.
It also worked just fine concurrently with trying to start a DBX for
more detailed information.

Yaarghhh!
dean