> On Sep 12, 2017, at 10:10 AM, Zachary Turner <ztur...@google.com> wrote: > > > > On Tue, Sep 12, 2017 at 10:03 AM Greg Clayton <clayb...@gmail.com > <mailto:clayb...@gmail.com>> wrote: >> On Sep 12, 2017, at 9:53 AM, Zachary Turner <ztur...@google.com >> <mailto:ztur...@google.com>> wrote: >> >> If you had just logged it, the bug would still not be fixed because nobody >> would know about it. I also can't believe we have to keep saying this :-/ > > By log, I mean Host::SystemLog(...) which would come out in the command line. > Not "log enable ...". So users would see the issue and report the bug. > Crashing doesn't mean people always report the bug. > I mentioned earlier in the thread that I assumed Xcode had an automatic crash > that would handle the crash and automatically upload it to Apple. Is this > really not the case? If core dumps are too big, why not just a stack trace? > Surely the Xcode team must have some kind of internal metrics system to track > stability.
They do just upload text crash logs. It doesn't tell us what expression triggered the issue though. It shows a crash in an expression, but doesn't show the expression text as this violates privacy.
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
