Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce "all-stop" setting #691

Open
eteran opened this Issue Dec 27, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@eteran
Copy link
Owner

eteran commented Dec 27, 2018

Getting the fine details of multi-threaded debugging is hard. edb currently still is a bit quirky on this front but works wonderfully when dealing with individual threads.

The idea here is to have a setting called "all-stop mode". The default would be enabled, which is essentially what edb currently attempts to do. That is, when an event comes in, it does its best to ensure that all other threads are paused to ensure a consistent debug state.

However, I have seen debuggers which don't pause all threads on an event, instead, they only worry about the thread which received the event. (gdb offers the ability to control this behavior calling it "all-stop mode as well :-P). All other threads keep on making whatever progress they can. When the setting is disabled, that's what edb would allow.

The caveat being that the application can change its state while you are looking at it, but if the user finds that useful, then that's OK.

@eteran eteran added the enhancement label Dec 27, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.