[lldb-dev] Detailed logging from test runs
zturner at google.com
Wed Dec 10 17:15:01 PST 2014
I'll look into -v tomorrow, not sure what it does. -t definitely isnt
enough though. I basically want all calls to LLDB's logging statements to
be output to a file somewhere when i run the test suite.
The reason this is useful is because i had a race condition that was
happening sporadically on different tests when run from the test runner,
but never individually. Attaching after the crash wasn't enough to figure
out what caused the error, since the crash was a symptom of something that
had happened earlier. So i wanted to see a full log for the crash run
On Wed, Dec 10, 2014 at 4:54 PM Greg Clayton <gclayton at apple.com> wrote:
> Try using "-t -v" when you need to see extra logging output from the test.
> Let me know if that isn't enough.
> > On Dec 10, 2014, at 1:42 PM, Zachary Turner <zturner at google.com> wrote:
> > Currently we just dump the results of stdout / stderr when running the
> tests. Occasionally it might be useful for someone diagnosing a failing
> test to enable more detailed logging. Essentially running a "log enable"
> command at lldb startup. I see that dotest.py has the ability to pass a
> runhook via -k, so that one could in theory run dotest.py -k "log enable
> > Is it worth putting this behind a separate option in dotest.py?
> Something like this:
> > dotest.py --enable-logging --log-filters=process|platform|communication
> > When --enable-logging is specified, the test runner would decide the
> output file name automatically using the value of the -s option, or if
> unspecified, the same default that -s uses.
> > _______________________________________________
> > lldb-dev mailing list
> > lldb-dev at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev