Hi

This happens seemingly at random , but frequent enough to be more than just
a nuisance and to have me worried. I might be in the middle of a debugging
session, then VS2012 suddenly disconnects - and the last thing I see in the
output is

09-09 17:53:58.275 I/dalvikvm( 5710): threadid=3: reacting to signal 3
09-09 17:53:58.280 I/dalvikvm( 5710): Wrote stack traces to
'/data/anr/traces.txt'
09-09 17:55:11.580 D/OpenGLRenderer( 5710): Flushing caches (mode 2)
09-09 17:55:11.885 D/OpenGLRenderer( 5710): Flushing caches (mode 0)
09-09 17:55:53.455 I/dalvikvm( 5710): threadid=3: reacting to signal 3
09-09 17:55:53.480 I/dalvikvm( 5710): Wrote stack traces to
'/data/anr/traces.txt'
The program 'Mono' has exited with code 255 (0xff).

Sometimes this goes along with an uncaught exception from the TPF - it seems
Tasks are used internally in M4A as well, and tasks that fault aren't
properly handled (you know... creating the task with a followup task
attached that handles the exception in case there's one, or calling
Task.Wait()) - and the funny thing is that I have attached the
UnobservedTaskException to the Task scheduler - so at least when you're on a
desktop, this means you catch any and all such exceptions, but it seems M4A
is wired differently and still manages to bomb out.

Feels like some bug to me, but before filing perhaps somebody can tell me a
bit about how I can extract more information than this to get a better idea
of what's going on.

Regards
Stephan



--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/Debugger-Disconnecting-sometimes-coupled-with-unhandled-TPF-exceptions-tp5711743.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
[email protected]

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Reply via email to