06-05-2013, 02:17 AM
I tried using DDMS to grab the stack trace of the app when it crashes, but because it just crashes instead of force closing, no traces or dumps are generated, and method profiling in DDMS/Eclipse just stops when the app crashes without generating the .trace file needed. I read the logcat again, and the app seems to be trying to access an invalid memory address or some read-only memory, so the OS is throwing a segmentation fault (the SIGSIEV at the end of the logcat) and then it kills the app.
As for the Java Stack Trace Console option, the logcat is not actually showing a "Caused By" error, so it can't be put into the stack trace console to find the offending code. It's probably going to need trial and error to track down exactly what is causing the problem. For now, all that is known is that attempting to progress past the first dialog prompt/menu makes the emu attempt to work with some protected memory, of which the OS detects and throws a segmentation fault.
As for the Java Stack Trace Console option, the logcat is not actually showing a "Caused By" error, so it can't be put into the stack trace console to find the offending code. It's probably going to need trial and error to track down exactly what is causing the problem. For now, all that is known is that attempting to progress past the first dialog prompt/menu makes the emu attempt to work with some protected memory, of which the OS detects and throws a segmentation fault.