That was using 4.2.3 :-/
I rolled back to 4.1 which appeared to fixed the breakpoint issue (maybe it
hadn't installed correctly?). I'm not quite brave enough to try 4.2.3 again
just yet.
It's still disconnecting however.
I've done a test with a new android project:
public void RecursiveStupidity()
{
RecursiveStupidity();
}
protected override void OnCreate(Bundle bundle)
{
base.OnCreate(bundle);
// Set our view from the "main" layout resource
SetContentView(Resource.Layout.Main);
// Get our button from the layout resource,
// and attach an event to it
Button button =
FindViewById<Button>(Resource.Id.MyButton);
button.Click += delegate { RecursiveStupidity();
button.Text =
string.Format("{0} clicks!", count++); };
}
and the log (including clicking on the button) produces:
06-12 14:32:33.720 D/dalvikvm(23637): Late-enabling CheckJNI
06-12 14:32:33.785 I/dalvikvm(23637): Turning on JNI app bug workarounds for
target SDK version 8...
06-12 14:32:33.850 I/ActivityThread(23637): Pub
AndroidApplication1.AndroidApplication1.__mono_init__:
mono.MonoRuntimeProvider
06-12 14:32:33.855 D/dalvikvm(23637): Trying to load lib
/data/data/AndroidApplication1.AndroidApplication1/lib/libmonodroid.so
0x40d84438
06-12 14:32:33.855 D/dalvikvm(23637): Added shared lib
/data/data/AndroidApplication1.AndroidApplication1/lib/libmonodroid.so
0x40d84438
06-12 14:32:33.860 W/MonoDroid-Debugger(23637): Trying to initialize the
debugger with options:
--debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8867,server=y,embedding=1
06-12 14:32:33.940 W/MonoDroid-Debugger(23637): Accepted stdout connection:
44
06-12 14:32:34.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:34.330 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:34.720 E/mono (23637): WARNING: The runtime version supported
by this application is unavailable.
06-12 14:32:34.720 E/mono (23637): Using default runtime: v2.0.50727
06-12 14:32:34.800 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:34.805 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:35.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:35.300 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:35.795 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:35.800 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:36.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:36.305 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:36.795 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:36.800 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:37.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:37.310 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:37.795 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:37.815 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:38.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:38.320 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:38.795 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:38.800 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:39.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:39.305 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:39.795 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:39.815 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:40.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:40.305 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:40.795 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:40.820 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:41.295 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:41.310 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
06-12 14:32:41.695 I/monodroid-gc(23637): environment supports jni
NewWeakGlobalRef
06-12 14:32:41.695 W/monodroid-gc(23637): GREF GC Threshold: 46800
Loaded assembly:
/data/data/AndroidApplication1.AndroidApplication1/files/.__override__/AndroidApplication1.dll
Loaded assembly: Mono.Android.dll [External]
Loaded assembly: System.Core.dll [External]
06-12 14:32:41.795 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:41.800 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
Loaded assembly: MonoDroidConstructors [External]
06-12 14:32:42.300 I/dalvikvm(23637): threadid=3: reacting to signal 3
06-12 14:32:42.310 I/dalvikvm(23637): Wrote stack traces to
'/data/anr/traces.txt'
The program 'Mono' has exited with code 255 (0xff).
It doesn't throw any stack overflow exceptions?
I'm assuming that this is happening in my actual application too...
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/debugger-constantly-detaches-tp5710262p5710298.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
