-
Notifications
You must be signed in to change notification settings - Fork 16
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
Threads handling #19
Comments
The continue command continues all threads. It would certainly be a little less ambiguous to add the word 'all' in there, so that the help read: "The continue (or c) command continues all threads until the next breakpoint occurs." |
You can use 'where all' to list the callstacks of all threads, which is a way also of seeing how many threads there are. There is no command list to list how many threads there are. |
The new github works horribly with my browser and I can't edit the previous command. I should have said "There is no command JUST to list how many threads there are." |
Ha ha I should have written "I can't edit the previous COMMENT." |
Two things:
Is there a way to get a list of all currently running threads? This should probably be a
threads
command.It's a bit confusing to understand what
continue
does in a threaded environment. From thecontinue
documentation:From the
thread
documentation:The question is: Does
continue
continue execution of all threads or just the current thread? If it's the latter, how do we get back to an "execute all threads" state?The text was updated successfully, but these errors were encountered: