On Fri, Apr 15, 2011 at 10:20 AM, Eric <[email protected]> wrote: > What else do you want to know?? >
To quote myself: "... all the relevant variables (OS, Eclipse version, ADT version, any logs, etc, etc)". > When I run it outside the debugger, it performs satisfactorily. The only > changing variable is the debugger. > The debugger is not a monolithic thing - many things can go wrong. Your USB connection could be fried. You could have faulty installation of Eclipse that breaks the debugger. You could be calling a function that sleeps for 1 second at a time if the debugger is attached, for all we know. > We can pretend the debugger is fast, like some of the follow up posts have > done > I don't think any of us stating our environments work fine are "pretending". > or we can discuss why Google can't provide developers with a decent > debugging environment (LET ALONE a simulator that is even remotely usable). > Or you could stop ranting and follow the steps I outlined in my first post to post *useful* feedback about the problem you're having via the appropriate channels. Assuming you actually want help with the issue and are not just venting. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
