-
Notifications
You must be signed in to change notification settings - Fork 343
[lldb] Introduce backtracing of Swift Tasks #9845
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
[lldb] Introduce backtracing of Swift Tasks #9845
Conversation
@swift-ci test |
@swift-ci test |
@swift-ci test |
CommandObjectLanguageSwiftTask(CommandInterpreter &interpreter) | ||
: CommandObjectMultiword( | ||
interpreter, "task", "Commands for inspecting Swift Tasks.", | ||
"language swift task <subcommand> [<subcommand-options>]") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Side note: Should we add an alias task
= language swift task
or (maybe less controversial) swift
= language swift
that is on by default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related: is swift-healthcheck
an alias for language swift healthcheck
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add an alias
task
=language swift task
or (maybe less controversial)swift
=language swift
that is on by default?
one of these two would be nice, I guess the question then is which one.
Related: is
swift-healthcheck
an alias forlanguage swift healthcheck
?
it's not currently, but we could switch it to that.
CommandObjectLanguageSwiftTask(CommandInterpreter &interpreter) | ||
: CommandObjectMultiword( | ||
interpreter, "task", "Commands for inspecting Swift Tasks.", | ||
"language swift task <subcommand> [<subcommand-options>]") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related: is swift-healthcheck
an alias for language swift healthcheck
?
Introduces the first of a new group of commands for working with Swift Task instances. The new command group is `language swift task`, and the first command is `backtrace`. This `backtrace` command takes the name of a task variable and prints the task's backtrace. The variable can be either `Task<Success, Failure>` or `UnsafeCurrentTask`. The output is similar to the builtin `thread backtrace` (`bt`) command. See the original PR: #9787
Introduces the first of a new group of commands for working with Swift Task instances. The new command group is `language swift task`, and the first command is `backtrace`. This `backtrace` command takes the name of a task variable and prints the task's backtrace. The variable can be either `Task<Success, Failure>` or `UnsafeCurrentTask`. The output is similar to the builtin `thread backtrace` (`bt`) command. See the original PR: #9787 (cherry picked from commit 2c3335d)
Introduces the first of a new group of commands for working with Swift Task instances.
The new command group is
language swift task
, and the first command isbacktrace
. Thisbacktrace
command takes the name of a task variable and prints the task's backtrace. The variable can be eitherTask<Success, Failure>
orUnsafeCurrentTask
. The output is similar to the builtinthread backtrace
(bt
) command.See the original PR: #9787