So much of the useful bug reporting information in lldb is gathered by turning on logs BEFORE the bad thing occurs, then making it happen, then gathering the logs that were produced as a part of that process. For instance, once a bad unwind has occurred that info is cached, and you can't watch lldb figure that out any more. And for expressions or stepping, you really can't do much after the fact.
So maybe a transactional design might be better, where you say (lldb) bugreport begin <AREA> ... (lldb) do stuff (lldb) bugreport end <AREA> or if you want them to nest you might hand back a token, but that seems over-designing. http://reviews.llvm.org/D10868 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ lldb-commits mailing list lldb-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
