title: Breakpoints not getting hit in Android Studio
body: <p>I'm using Windows 7 and have recently switched from Eclipse to Android Studio. I am now having trouble debugging.</p>
  
  <p>Running Android Studio 0.8.6, I set up a completely default install, I create a default empty project, targeting the ICS SDK, using the new project wizard. I then put a breakpoint in onCreate, click on the debug button and run.</p>
  
  <p>The debugger attached as I can see the message "Connected to the target VM" in the debugger window.</p>
  
  <p>I know the code is being executed because I am updating some text in the UI to show this.</p>
  
  <p>I have tried putting breakpoints in many places but none are hit.</p>
  
  <p>I'm pulling my hair out here as I just cannot see what I am doing wrong. I'm new to gradle so I think there may be some settings in gradle that I should be changing, but surely an absolutely standard project built with the wizard should let me hit breakpoints?</p>
  
  <p>One thing I noticed is that in my build.gradle file there is no mention of a debug build, only a release. I wondered if that might be the problem?</p>
  
  <pre><code>buildTypes {
      release {
          runProguard false
          proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
      }
  }
  </code></pre>
  
  <p>Note. I have tried this on both my own device and the emulator</p>
  
  <p>UPDATE:</p>
  
  <p>I changed the settings in the View Breakpoints options to turn on "Java Exception Breakpoints" but only for uncaught exceptions. Then, at the end of onCreate I deliberately cause a NullPointerException. When I run in debug now, I still don't hit my actual code and don't see the code break on my source, but the program does pause. I know it is my NullPointerException that is causing this because when I remove it, I can see that the code continues and does not break.</p>
  
  <p>At the point that my code breaks the debug window shows that I am in the "main" thread, in a function called "performLaunchActivity". I cannot see any more information than this. Presumably therefore I am debugging through whatever level of code is calling performLaunchActivity but that my source is being treated as if I can't step through it?</p>