I have had it running on a Nexus S and more recently on a Motorola Xoom (the original version, not Xoom 2). The Xoom is somewhat more practical as it has more CPU clout and more memory.
That said however, running any real sized application (anything that wants to do graphics, I think) requires a bunch of hoop jumping as detailed in https://blog.mozilla.com/jseward/2011/09/27/valgrind-on-android-current- status/ which actually makes it all quite difficult. A possible approach is to arrange your app so you can also build it on vanilla linux, and Valgrind it on there. Of course then you'd miss out on checking the Android specific parts. J On Friday, February 24, 2012, Scott Sibley wrote: > I'm in the market for a device so I can use valgrind to check memory errors > and leaks in my app. Which Samsung device is supported? I see a Galaxy S LL > Epic, a Galaxy S Fascinate, Galaxy S II (although I doubt it's this one), > and I think there's just a Galaxy S, but I'm unable to find much info on > this one, so I may be mistaken. > > I'd rather go with the phone more than I want to go with Pandaboard if I > can help it. > > Any hints? ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
