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 by: Brock Boland on 17 3월, 2014 Reason: Paragraph tags added automatically from tizen_format_fix module.