Aus deinem Log konnte ich folgendes rauslesen:

06-10 18:00:47.810: W/WindowManager(191): Force-removing child win Window{4120e7b0 SurfaceView paused=false} from container Window{411e09e8 com.al.triangle/hyem.Activity1 paused=false} 06-10 18:00:47.810: W/ActivityManager(191): Force removing ActivityRecord{413f5620 com.al.triangle/hyem.Activity1}: app died, no saved state
06-10 18:00:47.810: W/WindowManager(191): Failed looking up window
06-10 18:00:47.810: W/WindowManager(191): java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@412d51d8 does not exist Your View doesnt exists on stackoverflow i have seen a Text where the User with the Line ' android:stateNotNeeded="true" ' fixed this behaviour but i had not tested it.

also you allocate much objects i think the ddms could give you more information what is loaded to use
http://developer.android.com/guide/developing/debugging/ddms.html

you have many GCs in your Application is it also on a Run without the debugger? 06-10 18:00:40.100: I/dalvikvm-heap(14987): Grow heap (frag case) to 7.305MB for 672016-byte allocation 06-10 18:00:40.140: D/dalvikvm(14987): GC_FOR_ALLOC freed 0K, 8% free 7295K/7879K, paused 11ms 06-10 18:00:40.170: D/dalvikvm(14987): GC_FOR_ALLOC freed 688K, 16% free 6639K/7879K, paused 15ms 06-10 18:00:40.190: I/dalvikvm-heap(14987): Grow heap (frag case) to 18.791MB for 12716168-byte allocation

Am 10.06.2012 um 19:03 schrieb l0nestar:

I can’t see anything that hints at failure from logcat at all. I’ve attached
the whole log from start to finish for completeness.

http://mono-for-android.1047100.n5.nabble.com/file/n5710269/log.txt log.txt

Some way in to my code I have put a breakpoint on a Log.Debug call.. the debugger never hits it.. but the debug message itself does output to logcat.
(many times..) 

Looking at the build output - just noticed that visual studio holds on to this file after its finished debugging, and subsequent rebuilds create this:

HyemDroid -> <snip>\bin\Debug\Hyem.dll
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : The process cannot access the file <snip>\bin\Debug\Hyem.dll.mdb' because it is
being used by another process.
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : at
System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access,
Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize,
FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean
bFromProxy, Boolean useLongPath)
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : at Mono .CompilerServices.SymbolWriter.MonoSymbolWriter.WriteSymbolFile(Guid
guid)
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : at
Pdb2Mdb.Converter.Convert(AssemblyDefinition assembly, IEnumerable`1
functions, MonoSymbolWriter mdb)
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : at
Pdb2Mdb.Converter.Convert(String filename)
C:\Program Files
(x86)\MSBuild\Novell\Novell.MonoDroid.Common.targets(988,2): warning : at
Xamarin.Android.Tasks.ConvertDebuggingFiles.Execute()
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

Although it isn’t counted as an error… Restarting VS makes it go away.
(although I have to do this after every debug session  )

--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/debugger-constantly-detaches-tp5710262p5710269.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

_______________________________________________
Monodroid mailing list
[email protected]

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

Reply via email to