[Lldb-commits] [PATCH] Add new bugreport command to lldb

Tamas Berghammer tberghammer at google.com
Wed Jul 1 10:25:40 PDT 2015


I agree that we can collect only a very limited information with a single command after the problem already occurred but my intuition is that if we want the user to reproduce the issue then there is much lower chance that they will submit a bug report even for people working on LLDB.

For stack unwinding in special it is significantly easier to find out what was the issue if we have logs but in most of the case the information I display also sufficient (usually the CFI is the part what is incorrect). I think the same is true for expression evaluation with the only different that we should ask the user to specify the expression for the bugreport command (or we can try to find it on the command history).


http://reviews.llvm.org/D10868

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/






More information about the lldb-commits mailing list