OK, great. I've also found a workaround for the current version - select "Wait for Debugger" and the activity in the device's debug settings, then hit debug with the "Native Debug" run configuration selected. Once the native debug console shows the native debugger has attached, it's possible to use "connect to process" to connect the Java one, which also dismisses the "Waiting For Debugger" dialog and starts the code. Breakpoints on both sides get hit correctly.
On Wednesday, August 5, 2015 at 12:23:01 AM UTC+1, Johan Euphrosine wrote: > > > The "Native Debug" configuration doesn't cause the app to wait until the > debugger has connected. > > I believe this is fixed in the studio-1.4-dev branch. -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
