[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
getting a stack trace
- To: <xtech>
- Subject: getting a stack trace
- From: Eric Dean Tribble <tribble>
- Date: Fri, 4 May 90 16:43:32 PDT
If you just want a stack trace for your crashed program, and you don't
want to wait an hour, try adb!
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.