[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.
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.
Related: is swift-healthcheck an alias for language swift healthcheck?
There was a problem hiding this comment.
Should we add an alias
task=language swift taskor (maybe less controversial)swift=language swiftthat is on by default?
one of these two would be nice, I guess the question then is which one.
Related: is
swift-healthcheckan 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.
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. Thisbacktracecommand 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