[Lldb-commits] [lldb] [lldb] Fix `thread backtrace --count` (PR #83602)

2024-03-01 Thread Jonas Devlieghere via lldb-commits
https://github.com/JDevlieghere closed https://github.com/llvm/llvm-project/pull/83602 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb] Fix `thread backtrace --count` (PR #83602)

2024-03-01 Thread via lldb-commits
https://github.com/jimingham approved this pull request. LGTM. We really need to get option values to parse somewhere more generically so we don't have to change so many places just to get a good error for value conversion, but that's not this PR's fault... https://github.com/llvm/llvm-projec

[Lldb-commits] [lldb] [lldb] Fix `thread backtrace --count` (PR #83602)

2024-03-01 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Jonas Devlieghere (JDevlieghere) Changes The help output for `thread backtrace` specifies that you can pass -1 to `--count` to display all the frames. ``` -c ( --count ) How many frames to display (-1 for all) `

[Lldb-commits] [lldb] [lldb] Fix `thread backtrace --count` (PR #83602)

2024-03-01 Thread Jonas Devlieghere via lldb-commits
https://github.com/JDevlieghere created https://github.com/llvm/llvm-project/pull/83602 The help output for `thread backtrace` specifies that you can pass -1 to `--count` to display all the frames. ``` -c ( --count ) How many frames to display (-1 for all) ``` However, that does