Jonathan Pryor | 7 Jan 04:33 2013

Re: Copying data between Dalvik and Mono... major slowdown.

On Jan 3, 2013, at 4:32 PM, Jeremy A. Kolb - ARA/NED <jkolb@...> wrote:
> Furthermore, In:
>  
>     [Register("bulkInsert", "(Landroid/net/Uri;[Landroid/content/ContentValues;)I", "")]
>     public int BulkInsert(Android.Net.Uri url, ContentValues[] values)
>     {
>       IntPtr num1 = JNIEnv.NewArray<ContentValues>(values);
>       ...
>       if (values != null)
>       {
>         JNIEnv.CopyArray<ContentValues>(num1, values);
>         JNIEnv.DeleteLocalRef(num1);
>       }
>       return num2;
>     }
>  
> Why is the array copied back in after the function call? values shouldn’t have changed.

_You_ know that. The generator does not; it can change on a method-by-method basis, and the generator needs
to generate code to support it.

>  url certainly doesn’t get the same treatment.

`url` isn't an array, and thus has "pass by value" semantics.

For example, consider this potential Java method:

	public int bulkInsert(Uri url, ContentValues[] values) {
		url = new Url (...);
		values [0] = new ContentValues (...);
(Continue reading)

Willem Meints | 7 Jan 13:54 2013

Re: Copying data between Dalvik and Mono... major slowdown.

Isn't it a good solution to exclude the method from being mapped in the metadata.xml and hand-write the code instead?
It certainly doesn't look all THAT difficult in this case.

Kind regards,
 
Willem Meints
Lead Developer
Professional Development Centre
 
mobile: +31 (0)6 47 506 037

-----Oorspronkelijk bericht-----
Van: monodroid-bounces@...
[mailto:monodroid-bounces@...ian.com] Namens Jonathan Pryor
Verzonden: maandag 7 januari 2013 04:34
Aan: Discussions related to Mono for Android
Onderwerp: Re: [mono-android] Copying data between Dalvik and Mono... major slowdown.

On Jan 3, 2013, at 4:32 PM, Jeremy A. Kolb - ARA/NED <jkolb@...> wrote:
> Furthermore, In:
>  
>     [Register("bulkInsert", "(Landroid/net/Uri;[Landroid/content/ContentValues;)I", "")]
>     public int BulkInsert(Android.Net.Uri url, ContentValues[] values)
>     {
>       IntPtr num1 = JNIEnv.NewArray<ContentValues>(values);
>       ...
>       if (values != null)
>       {
>         JNIEnv.CopyArray<ContentValues>(num1, values);
>         JNIEnv.DeleteLocalRef(num1);
(Continue reading)

Jeremy A. Kolb - ARA/NED | 7 Jan 14:51 2013

Re: Copying data between Dalvik and Mono... major slowdown.

I had a feeling that was why.  Anyway I wrote my own implementation in C# using Mono.Data.Sqlite with my own
version of the ContentValues class.  It now executes in 1/4 of the time.

-----Original Message-----
From: monodroid-bounces@...
[mailto:monodroid-bounces@...] On Behalf Of Jonathan Pryor
Sent: Sunday, January 06, 2013 10:34 PM
To: Discussions related to Mono for Android
Subject: Re: [mono-android] Copying data between Dalvik and Mono... major slowdown.

On Jan 3, 2013, at 4:32 PM, Jeremy A. Kolb - ARA/NED <jkolb@...> wrote:
> Furthermore, In:
>  
>     [Register("bulkInsert", "(Landroid/net/Uri;[Landroid/content/ContentValues;)I", "")]
>     public int BulkInsert(Android.Net.Uri url, ContentValues[] values)
>     {
>       IntPtr num1 = JNIEnv.NewArray<ContentValues>(values);
>       ...
>       if (values != null)
>       {
>         JNIEnv.CopyArray<ContentValues>(num1, values);
>         JNIEnv.DeleteLocalRef(num1);
>       }
>       return num2;
>     }
>  
> Why is the array copied back in after the function call? values shouldn't have changed.

_You_ know that. The generator does not; it can change on a method-by-method basis, and the generator needs
to generate code to support it.
(Continue reading)

Jonathan Chapman | 7 Jan 17:24 2013

Debugging in 4.4.54 crashes

I just upgraded to 4.4.54 (After 4.4.41 failed and I had to use for 4.2.7 for
a while because of the license issue.)  The application seems to work but
the debugging crashes.  The application is quite large with a lot of
threaded code.  The one spot it seems to crash most times is in a chunk of
code that is in a thread.  If I place a breakpoint in the code and step
through most times it will not crash.

If I'm not debugging but I'm running the debug code it doesn't crash.

Again this has worked for a long time before the upgrade.

I'm not seeing much in the log.  This is what it says:

01-07 11:00:57.630 D/AndroidRuntime(13086): 
01-07 11:00:57.630 D/AndroidRuntime(13086): >>>>>> AndroidRuntime START
com.android.internal.os.RuntimeInit <<<<<<
01-07 11:00:57.630 D/AndroidRuntime(13086): CheckJNI is OFF
01-07 11:00:57.638 D/dalvikvm(13086): Trying to load lib libjavacore.so 0x0
01-07 11:00:57.638 D/dalvikvm(13086): Added shared lib libjavacore.so 0x0
01-07 11:00:57.646 D/dalvikvm(13086): Trying to load lib libnativehelper.so
0x0
01-07 11:00:57.646 D/dalvikvm(13086): Added shared lib libnativehelper.so
0x0
01-07 11:00:57.786 D/AndroidRuntime(13086): Calling main entry
com.android.commands.am.Am
01-07 11:00:57.794 I/ActivityManager(28606): START
{act=android.intent.action.MAIN cat=[android.intent.category.HOME]
flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher u=0}
from pid 12985
01-07 11:00:57.849 I/AndroidRuntime(12985): VM exiting with result code -1,
(Continue reading)

Jonathan Chapman | 7 Jan 17:26 2013

Re: Debugging in 4.4.54 crashes

One additional point this has been tried on an Acer 500 and a Samsung Galaxy
Nexus running 4.1.1.  With an application that has a minimum of 4.0.

Jonathan

--
View this message in context: http://mono-for-android.1047100.n5.nabble.com/Debugging-in-4-4-54-crashes-tp5712705p5712706.html
Sent from the Mono for Android mailing list archive at Nabble.com.
Jonathan Pryor | 7 Jan 21:41 2013

Re: Debugging in 4.4.54 crashes

On Jan 7, 2013, at 11:24 AM, Jonathan Chapman
<jonathan_Chapman@...> wrote:
> I just upgraded to 4.4.54...The application seems to work but the debugging crashes.  The application is
quite large with a lot of threaded code.  The one spot it seems to crash most times is in a chunk of code that is
in a thread.  If I place a breakpoint in the code and step through most times it will not crash.

Just so I'm understanding this properly:

If you don't debug, the program executes properly.

If you debug, the program will crash, UNLESS you set a breakpoint "somewhere" and step through there.

Could you please file a bug at bugzilla.xamarin.com and attach your project so our debugging experts can investigate?

Thanks,
 - Jon

Jonathan Chapman | 7 Jan 21:48 2013

Re: Debugging in 4.4.54 crashes

That is correct.  I will file the bug.
 

Jonathan Chapman

 

From: Jonathan Pryor-2 [via Mono for Android] [mailto:[hidden email]]
Sent: Monday, January 07, 2013 3:42 PM
To: Jonathan Chapman
Subject: Re: Debugging in 4.4.54 crashes

On Jan 7, 2013, at 11:24 AM, Jonathan Chapman <[hidden email]> wrote:
> I just upgraded to 4.4.54...The application seems to work but the debugging crashes.  The application is quite large with a lot of threaded code.  The one spot it seems to crash most times is in a chunk of code that is in a thread.  If I place a breakpoint in the code and step through most times it will not crash.

Just so I'm understanding this properly:

If you don't debug, the program executes properly.

If you debug, the program will crash, UNLESS you set a breakpoint "somewhere" and step through there.

Could you please file a bug at bugzilla.xamarin.com and attach your project so our debugging experts can investigate?

Thanks,
 - Jon

_______________________________________________
Monodroid mailing list
[hidden email]

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


If you reply to this email, your message will be added to the discussion below:
http://mono-for-android.1047100.n5.nabble.com/Debugging-in-4-4-54-crashes-tp5712705p5712707.html
To unsubscribe from Debugging in 4.4.54 crashes, click here.
NAML

View this message in context: RE: Debugging in 4.4.54 crashes
Sent from the Mono for Android mailing list archive at Nabble.com.
<div>
<div dir="ltr" align="left"><span class="274424520-07012013">That is correct.&nbsp; I will file the 
bug.</span></div>
<div>&nbsp;</div>
<div align="left">
<p class="MsoNormal"><span>Jonathan 
Chapman</span></p>
</div>
<div>&nbsp;</div>
<br><div lang="en-us" class="OutlookMessageHeader" dir="ltr" align="left">
From: Jonathan Pryor-2 [via Mono for Android] 
[mailto:<a href="/user/SendEmail.jtp?type=node&amp;node=5712708&amp;i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>] <br>Sent: Monday, 
January 07, 2013 3:42 PM<br>To: Jonathan Chapman<br>Subject: Re: 
Debugging in 4.4.54 crashes<br><br>
</div>
<div></div>On Jan 7, 2013, at 11:24 AM, Jonathan Chapman &lt;<a href="/user/SendEmail.jtp?type=node&amp;node=5712707&amp;i=0" rel="nofollow" target="_top" link="external">[hidden email]</a>&gt; wrote: <br>&gt; I just 
upgraded to 4.4.54...The application seems to work but the debugging crashes. 
&nbsp;The application is quite large with a lot of threaded code. &nbsp;The one 
spot it seems to crash most times is in a chunk of code that is in a thread. 
&nbsp;If I place a breakpoint in the code and step through most times it will 
not crash. <br><br>Just so I'm understanding this properly: <br><br>If you don't 
debug, the program executes properly. <br><br>If you debug, the program will 
crash, UNLESS you set a breakpoint "somewhere" and step through there. 
<br><br>Could you please file a bug at bugzilla.xamarin.com and attach your 
project so our debugging experts can investigate? <br><br>Thanks, <br>&nbsp;- 
Jon <br><br>_______________________________________________ <br>Monodroid 
mailing list <br><a href="/user/SendEmail.jtp?type=node&amp;node=5712707&amp;i=1" rel="nofollow" target="_top" link="external">[hidden email]</a> <br><br>UNSUBSCRIBE INFORMATION: 
<br><a href="http://lists.ximian.com/mailman/listinfo/monodroid" rel="nofollow" target="_top" link="external">http://lists.ximian.com/mailman/listinfo/monodroid</a><br><br><br><div>
<div>If you reply to this email, your message will be 
added to the discussion below:</div>
<a href="http://mono-for-android.1047100.n5.nabble.com/Debugging-in-4-4-54-crashes-tp5712705p5712707.html" target="_top" rel="nofollow" link="external">http://mono-for-android.1047100.n5.nabble.com/Debugging-in-4-4-54-crashes-tp5712705p5712707.html</a> 
</div>
<div>To 
unsubscribe from Debugging in 4.4.54 crashes, <a href="" target="_top" rel="nofollow" link="external">click 
here</a>.<br><a href="http://mono-for-android.1047100.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&amp;id=instant_html%21nabble%3Aemail.naml&amp;base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&amp;breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" rel="nofollow" target="_top" link="external">NAML</a> </div>

	
	
	
<br>
View this message in context: <a href="http://mono-for-android.1047100.n5.nabble.com/Debugging-in-4-4-54-crashes-tp5712705p5712708.html">RE: Debugging in 4.4.54 crashes</a><br>
Sent from the <a href="http://mono-for-android.1047100.n5.nabble.com/">Mono for Android mailing list archive</a> at Nabble.com.<br>
</div>
admin | 7 Jan 22:21 2013
Picon

OutOfMemoryError

Hi,

I have app with several common images on ui. When I navigate between 
activities some times throw exception.
I have standard emulator with 256mb ram.
What is cause of this?

144000-byte external allocation too large for this process.
VM won't let us allocate 144000 bytes
Shutting down VM
FATAL EXCEPTION: main
java.lang.OutOfMemoryError: bitmap size exceeds VM budget
	at android.graphics.Bitmap.nativeCreate(Native Method)
	at android.graphics.Bitmap.createBitmap(Bitmap.java:477)
	at com.tapfortap.AdView.scale(AdView.java:403)
	at com.tapfortap.AdView.onDraw(AdView.java:164)
	at android.view.View.draw(View.java:6880)
	at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
	at android.view.View.draw(View.java:6883)
	at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
	at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
	at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
	at android.view.View.draw(View.java:6883)
	at android.widget.FrameLayout.draw(FrameLayout.java:357)
	at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
	at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
	at android.view.View.draw(View.java:6883)
	at android.widget.FrameLayout.draw(FrameLayout.java:357)
	at 
com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1862)
	at android.view.ViewRoot.draw(ViewRoot.java:1522)
	at android.view.ViewRoot.performTraversals(ViewRoot.java:1258)
	at android.view.ViewRoot.handleMessage(ViewRoot.java:1859)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:123)
	at android.app.ActivityThread.main(ActivityThread.java:3683)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:507)
	at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
	at dalvik.system.NativeStart.main(Native Method)
Sending signal. PID: 1903 SIG: 9
Jonathan Chapman | 7 Jan 23:06 2013

Library Layouts and Drawables

We had a large library of resources that we used to just link in because
Android resources could not be in libraries.  I just upgraded to the latest
and have spent all day converting the library to a true library.  I've just
gotten to the point where everything seems fine except in the UpdateIdValues
where it does the mapping it's trying to map something like

Library.Drawable.GreyLine = Application.Resource.Drawable.GreyLine;

However in Application the resource id was generated as all lower case
instead of mixed case.  Mixed Case would be correct.  Please confirm this is
a bug and then I'll temporarily change my library resource to be all lower
case.

Note that some things like Strings, styles and id's work.  Just Layours,
Menu, and Drawables do not.

Regards,
Jonathan

--
View this message in context: http://mono-for-android.1047100.n5.nabble.com/Library-Layouts-and-Drawables-tp5712710.html
Sent from the Mono for Android mailing list archive at Nabble.com.
Tom Opgenorth | 8 Jan 00:16 2013
Picon

Re: OutOfMemoryError

Your bitmaps are using up all of the memory available. You might want to scale down the bitmaps - check out this recipe: http://docs.xamarin.com/android/Recipes/Resources/General/Load_Large_Bitmaps_Efficiently


On Mon, Jan 7, 2013 at 2:21 PM, <admin-KHK8YizctYMYDkwjdqtpGQ@public.gmane.org> wrote:
Hi,

I have app with several common images on ui. When I navigate between activities some times throw exception.
I have standard emulator with 256mb ram.
What is cause of this?

144000-byte external allocation too large for this process.
VM won't let us allocate 144000 bytes
Shutting down VM
FATAL EXCEPTION: main
java.lang.OutOfMemoryError: bitmap size exceeds VM budget
        at android.graphics.Bitmap.nativeCreate(Native Method)
        at android.graphics.Bitmap.createBitmap(Bitmap.java:477)
        at com.tapfortap.AdView.scale(AdView.java:403)
        at com.tapfortap.AdView.onDraw(AdView.java:164)
        at android.view.View.draw(View.java:6880)
        at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
        at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
        at android.view.View.draw(View.java:6883)
        at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
        at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
        at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
        at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
        at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
        at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
        at android.view.View.draw(View.java:6883)
        at android.widget.FrameLayout.draw(FrameLayout.java:357)
        at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
        at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
        at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
        at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
        at android.view.View.draw(View.java:6883)
        at android.widget.FrameLayout.draw(FrameLayout.java:357)
        at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1862)
        at android.view.ViewRoot.draw(ViewRoot.java:1522)
        at android.view.ViewRoot.performTraversals(ViewRoot.java:1258)
        at android.view.ViewRoot.handleMessage(ViewRoot.java:1859)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:123)
        at android.app.ActivityThread.main(ActivityThread.java:3683)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:507)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
        at dalvik.system.NativeStart.main(Native Method)
Sending signal. PID: 1903 SIG: 9
_______________________________________________
Monodroid mailing list
Monodroid <at> lists.ximian.com

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



--
http://www.opgenorth.net
<div>
<div dir="ltr">Your bitmaps are using up all of the memory available. You might want to scale down the bitmaps - check out this recipe:&nbsp;<a href="http://docs.xamarin.com/android/Recipes/Resources/General/Load_Large_Bitmaps_Efficiently">http://docs.xamarin.com/android/Recipes/Resources/General/Load_Large_Bitmaps_Efficiently</a>
</div>

<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 2:21 PM,  <span dir="ltr">&lt;<a href="mailto:admin <at> flatplanet.pl" target="_blank">admin@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">

Hi,<br><br>
I have app with several common images on ui. When I navigate between activities some times throw exception.<br>
I have standard emulator with 256mb ram.<br>
What is cause of this?<br><br>
144000-byte external allocation too large for this process.<br>
VM won't let us allocate 144000 bytes<br>
Shutting down VM<br>
FATAL EXCEPTION: main<br>
java.lang.OutOfMemoryError: bitmap size exceeds VM budget<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.graphics.Bitmap.nativeCreate(Native Method)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.graphics.Bitmap.createBitmap(Bitmap.java:477)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at com.tapfortap.AdView.scale(AdView.java:403)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at com.tapfortap.AdView.onDraw(AdView.java:164)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.View.draw(View.java:6880)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.drawChild(ViewGroup.java:1646)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.View.draw(View.java:6883)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.drawChild(ViewGroup.java:1646)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.drawChild(ViewGroup.java:1644)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.drawChild(ViewGroup.java:1644)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.View.draw(View.java:6883)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.widget.FrameLayout.draw(FrameLayout.java:357)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.drawChild(ViewGroup.java:1646)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.drawChild(ViewGroup.java:1644)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.View.draw(View.java:6883)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.widget.FrameLayout.draw(FrameLayout.java:357)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1862)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewRoot.draw(ViewRoot.java:1522)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewRoot.performTraversals(ViewRoot.java:1258)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.view.ViewRoot.handleMessage(ViewRoot.java:1859)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.os.Handler.dispatchMessage(Handler.java:99)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.os.Looper.loop(Looper.java:123)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at android.app.ActivityThread.main(ActivityThread.java:3683)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at java.lang.reflect.Method.invokeNative(Native Method)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at java.lang.reflect.Method.invoke(Method.java:507)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)<br>
&nbsp; &nbsp; &nbsp; &nbsp; at dalvik.system.NativeStart.main(Native Method)<br>
Sending signal. PID: 1903 SIG: 9<br>
_______________________________________________<br>
Monodroid mailing list<br><a href="mailto:Monodroid@..." target="_blank">Monodroid <at> lists.ximian.com</a><br><br>
UNSUBSCRIBE INFORMATION:<br><a href="http://lists.ximian.com/mailman/listinfo/monodroid" target="_blank">http://lists.ximian.com/mailman/listinfo/monodroid</a><br>
</blockquote>
</div>
<br><br clear="all"><div><br></div>-- <br><a href="http://www.opgenorth.net" target="_blank">http://www.opgenorth.net</a>
</div>
</div>

Gmane