Is there any way to get any useful information out of the call stack? I just get a bunch of memory addresses for the executable and cryptically named so files. Can I link the source in some way so the memory addresses match to the source and so it shows the actual stack trace with function names?
Crash Call Stack
Edited on 18 03, 2014