[mono-android] [Monodroid] Getting Variable Values While Debugging

[Jon Valvatne]

Thanks for the reply. Your description is similar to what I've seen, though
lately I very rarely get anything other than "took too long" messages.

Since you mentioned the emulator I thought I'd try debugging on a device,
which I hadn't tried previously - I figured it might be just the emulator
that was slow. Unfortunately I'm getting very similar results there.

Has there been any official word on this from the Monodroid team?

Jon

On Tue, Mar 22, 2011 at 11:07 AM, Andrew Sinclair <andrew at magic5software.com
> wrote:

> Jon,
>
>
>
> I often see the same thing.
>
>
>
> Sometimes variable values are shown, but it takes a long time (eg. half a
> minute). Other times it just gives the “The expression evaluation took too
> long” message or there’s no message and it’s clearly given up trying.
>
>
>
> Sometimes in the Locals window the first batch of variable values are shown
> fine, the remainder have the “too long” message.
>
>
>
> FWIW I’m always debugging using the emulator.
>
>
>
> Andy
>
>
>
> *From:* monodroid-bounces at lists.ximian.com [mailto:
> monodroid-bounces at lists.ximian.com] *On Behalf Of *Jon Valvatne
> *Sent:* 22 March 2011 09:43
> *To:* monodroid at lists.ximian.com
> *Subject:* Re: [mono-android] [Monodroid] Getting Variable Values While
> Debugging
>
>
>
> I'm experiencing this as well, nearly two months later, but I haven't heard
> anyone else talking about it. I can't find it in Bugzilla either.
>
>
>
> So I guess I'd like the same quick sanity check Nathan requested - is this
> a known issue? Or is there something wrong with my MonoDroid installation?
>
> On Sun, Jan 30, 2011 at 9:38 PM, Nathan Blevins <
> nblevins at nathanblevins.com> wrote:
>
> Hey all,
>
>
>
> I know that performance has been on the list for a while now, but I wanted
> to have a quick sanity check.  Right now, my debugger is essentially useless
> for me.  Every request in the watch window or via hovering over variables
> while stopped will result in a timeout.  Is this the behavior that everyone
> else is experiencing?  The break points hit just fine, but I can't get any
> values from a stopped point due to errors like this:
>
>
>
> *Watch Window*
>
>
>
> Name:  item.GetType()
>
> Value:Unable to evaluate the expression. The expression evaluation took too
> long.
>
>
>
>
>
> Currently my workaround is that I write everything to console.  Feels
> almost like the old Javascript debugging days.  :)   The big downside here
> is that I am waiting 3-5 mins between each build which makes debugging SLOW.
>  What should take 10 mins of testing to fix is now taking up to an hour.
>
>
>
> Anyone else having better luck than I on this?
>
>
>
> Nathan
>
>
> _______________________________________________
> Monodroid mailing list
> Monodroid at lists.ximian.com
>
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/mailman/listinfo/monodroid
>
>
>
> _______________________________________________
> Monodroid mailing list
> Monodroid at lists.ximian.com
>
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/mailman/listinfo/monodroid
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/mailman/private/monodroid/attachments/20110322/0243563b/attachment.html