[mono-android] debugger constantly detaches

[Jonathan Pryor]

On Jun 9, 2012, at 9:07 AM, l0nestar wrote:
> I'm having serious issues debugging my application! If I start it with the debugger attached the app runs for about 5-10 seconds then shuts down. presumably because the debugger has detached.. but I cant find out why!

That does seem rather odd. You might try enabling additional diagnostic output to see where it gets before it dies:

	http://docs.xamarin.com/android/advanced_topics/diagnostics

> I've looked at the logcat output.. but i dont think that it contains much useful information (my app was PID 2013):
> 
> 06-09 13:50:17.980: D/dalvikvm(2013): GC_CONCURRENT freed 389K, 83% free 6590K/36807K, paused 2ms+4ms

Despite the first reply, Dalvik is stating that Dalvik has 83% free for your process. I don't think you're running out of Dalvik heap space.

> The end of the monodroid.log contains:
> 
> Finished OnTargetEvent: 1ms
> Starting OnTargetEvent: TargetExited: Backtrace: null, Thread: null,
> ProcessInfo: null
> - Finding event type..
> Entering OnTargetExited for:
> Mono.Android.VisualStudio.MonoAndroidDebuggerSession
> [D:RunShellCommand]:      015c7b47e90ffc10 am broadcast -a mono.android.intent.action.SEPPUKU -c mono.android.intent.category.SEPPUKU.com.al.triangle

The SEPPUKU handler source can be found in e.g. $(ProjectDir)\obj\Debug\android\src\mono\android\Seppuku.java. All it does is exit the process.

You're seeing this message because we do not support attaching to an existing process; the debugger needs to be present at process startup. The IDE sends the SEPPUKU message before starting a debug session to ensure that the previous process has exited.

Thanks,
 - Jon