Debugger reports other threads running when breakpoint hit #147

Closed
opened 2025-08-09 17:13:36 +00:00 by fergalmoran · 0 comments
Owner

Originally created by @adelphes on 1/27/2017

When a breakpoint is hit, the active thread is marked as paused and the call stack displayed - the other threads are marked as still running. This is incorrect - the debugger actually stops all threads.

This is apparent when a new thread is started and a breakpoint hit within it - the debugger shows the thread as paused, but the main UI thread is clearly paused too.

*Originally created by @adelphes on 1/27/2017* When a breakpoint is hit, the active thread is marked as paused and the call stack displayed - the other threads are marked as still running. This is incorrect - the debugger actually stops all threads. This is apparent when a new thread is started and a breakpoint hit within it - the debugger shows the thread as paused, but the main UI thread is clearly paused too.
fergalmoran added the bugbug labels 2025-08-09 17:13:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/android-dev-ext#147
No description provided.