This will display the list of existing breakpoints without the one we just deleted: > clearīreakpoint OurApplication.buildInstanceString(int)īreakpoint OurApplication.main(java.lang. First, within Android Studio, be sure to setup your Android Monitor to filter for Errors only to reduce noise. To verify whether the breakpoint has correctly been removed, we'll use clear without arguments. The identifier is exactly the same as the one used earlier with the command stop: > clear OurApplication:7
To achieve this, we'll use the command clear followed by the breakpoint's identifier. Now that we've evaluated all the variables we needed to, we'll want to delete the breakpoints set earlier and let the thread continue its processing. New OurApplication(10).instanceString = "10. We'll evaluate a new instance of OurApplication for which we've passed an integer as a constructor parameter: > print new OurApplication(10).instanceString As in the preceding image we can see the thread having no name. Working with Thread Window Now let's have a look at the Thread window. We can also see that print has exactly the same behavior as eval: they both evaluate an expression or a variable. Step 3 Click on the Debug menu and choose the windows option then select Threads as shown in the following image. Unlike the other variables, local variables don't require to specify a class or an instance. Next, let's see the variable i: > print i
0 kommentar(er)
