jingham added a comment. The thing the "bugreport unwind" adds is that it runs a handful of commands that gather data useful in diagnosing unwind problems. That's useful when the information you need might not be output by the session in which the bug appeared.
The same thing could be achieved by having "reproducer generate" take arguments that the user can specify to automate gathering more data that would be relevant to a particular kind of bug. So "bugreport unwind" -> "reproducer generate unwind" which would run the same extra commands that "bugreport unwind" does (the results will get captured by the same mechanism that's catching all the other session output) and then the reproducer would be generated. Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D65469/new/ https://reviews.llvm.org/D65469 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
