Bob, sorry I think I may have confused you. The debugger doesnt stop at all, I shouldnt have said the debugger doesnt stop at the exact point, which is completely untrue because it doesnt stop at all. Thanks for your detailed email, unfortunately that doesnt solve my problem.
On Apr 28, 1:46 am, Bob Kerns <r...@acm.org> wrote: > BTW, when you edit in the text of a message you're replying to this > way, the group software's link to email fails to include your > response. I had to go to the web to retrieve it. Extracting out the > relevant bit: > > * That the debugger supports breakpoints, and single stepping? > - i added a ttoggle breakpoint (by right clicking on the screen -> > toggle breakpoint) but the debugger doesnt stop at the exact point. > > * That the debugger also supports breaking on exceptions? > - I dont know, it doesnt stop on breakpoints. > > OK, so it appears the information you're missing is that the debugger > does, in fact, stop at breakpoints. And so therefore, there must be > something wrong that's leading to your observations. Without knowing > that, it's natural to think perhaps the debugger doesn't work... > > Here's what I'd suggest: First, DELETE your application from your > device. Make sure it's gone. > > Then, in the Package Explorer, right click on the top level of your > project folder, and choose Refresh. This will inform Eclipse about any > changes that may have been made to files outside Eclipse. > > Then, under the Project menu, choose Clean..., and select your project > to clean. This will remove any built files, and force a rebuild, to > ensure that the output files are in sync with the input files. > > Set a breakpoint on the first line of your first Activity's onCreate() > method. > > Switch to the Debug perspective, and choose the Breakpoints tab. > There's a little icon in the top bar of that view, that looks kind of > like "J!". This is where you set breakpoints on exceptions. Use that > to set breakpoints on RuntimeException and Error. > > Finally, with your device connected via USB, and debugging enabled on > the device, right click on the project folder in the Package Explorer, > and choose Debug As... / Android Application. > > It will install your application. You should see a dialog indicating > that your application is waiting for the debugger to connect. Then it > should stop in the debugger, and show you either your breakpoint, or > an exception being thrown if it isn't even getting that far. > > Also, if you switch to the DDMS perspective, at the bottom you should > see a LogCat window. At least, I think it's there by default... This > shows you the device's log as it happens. If you get an error (even > without debugging) that isn't caught, it'll show the stacktrace in > this window, as well as many other useful things. Too much, actually! > > You can get this view added to any perspective (such as the Debug > perspective) with File / Show View / Other..., and then expanding the > Android category and choosing LogCat. > > That SHOULD get you going. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group > athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
