Hi Jon, No, there's no particularly good reason why I'm using busybox, I forget even why it's there, so I can certainly work around the problem by uninstalling it. Strangely though, it's only become a problem with MfA 4.2.5. I can't say for sure that it didn't happen with earlier versions, but now it happens very consistently.
The output above was pulled from the dialog using Spy++ and some hacked up code to get the text from the window while the dialog was open (since the text isn't selectable/copyable). It's possible that it's been truncated on it's way to the dialog. I'll send the output of 'ps' received from a telnet session to that email address. Thanks, Paul On 18 August 2012 02:18, Jonathan Pryor <j...@xamarin.com> wrote: > On Aug 15, 2012, at 8:17 PM, psryland <psryl...@yahoo.co.nz> wrote: > > I've been noticing this deployment error a lot with the latest alpha > version of MfA (v4.2.5, installer: mono-android-4.2.5.195540401.msi). The > device I'm > > deploying to has this Busybox version: BusyBox v1.20.2-Stericson > (2012-07-04 21:33:31 CDT) > > Any particular reason you're using BusyBox? We parse ps(1) output for a > variety of reasons, and the BusyBox `ps` output is not at all what we're > expecting. Worse, it appears to be truncating process names... > > Could you please send an email to supp...@xamarin.com with your ps output > so that we can track this? > > Thanks, > - Jon > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid >
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
