clayborg added a comment.

IMHO: we should keep this command and expand its abilities to help report 
stepping issues, expression issues and more. Why? Getting good bug reports from 
users is quite hard. Allowing them to type "bugreport step --step-in" or 
"bugreport step --step-over" would be really nice. Right now I send people a 
python script that enables logging, dumps the code in and around the source 
line with disassembly, and creates a zip file with the current object file and 
optional debug info file (dSYM or external symbol file).

Happy to hear what others have to say though.


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

Reply via email to