<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Paul,</div><div class="">it’s hard to tell exactly what is going on in your situation without further details, but</div><div class=""><br class=""></div><div class="">a) is there any chance you can compile LLDB from sources and use that debugger to perform your automation?</div><div class="">The LLDB you would get that way is newer than the one you are trying to use right now (and we fix bugs all the time, so you do want as new as you can get)</div><div class=""><br class=""></div><div class="">Also,</div><div class="">b) if the debugger hangs or crashes, it’s a bug and it should be fixed - so, please file bugs for anything that does not work</div><div class="">And, again, if you are somewhat tracking our trunk, any and all bug fixes, you get much more rapidly than staying on released Xcode versions</div><div class=""><br class=""></div><div class="">c) Without further details (crash logs, samples, …) it’s hard to say what’s going on in your situation, so not much to comment here - except that LLDB should be mature enough to script (not via the command line, but using the SB API) - and anything that blocks that should be filed on the LLVM bugzilla as an issue</div><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 16, 2015, at 2:41 PM, Paul Smith <<a href="mailto:paul@mad-scientist.net" class="">paul@mad-scientist.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Sorry for the length here. TL;DR: is it possible to reliably script<br class="">LLDB non-interactively, or is this a known area of weakness in LLDB and<br class="">I should give up until LLDB gets more mature in this area?<br class=""><br class="">We have a script in our test environment to perform a basic triage of<br class="">coredumps that happen during testing; when a test detects a core it runs<br class="">this script to get some info about the failure: we can use the backtrace<br class="">to categorize the core, etc.<br class=""><br class="">On GNU/Linux it uses GDB to do some simple things like print some<br class="">important global variable values, show a full backtrace of all threads<br class="">(these programs often have 20+ threads active), show the environment,<br class="">etc. We give this little script to GDB with the "-batch -x <file>"<br class="">commands, and it works perfectly every time.<br class=""><br class="">Now we need to do the same thing for cores generated on Mac OSX (we're<br class="">using Xcode 5.1.1 but we've seen these same behaviors for older versions<br class="">as well).<br class=""><br class="">At first we were using the old GDB 6.3.50.20050815-cvs which is the last<br class="">one supported by Apple. This works fine if we have a full set of object<br class="">files, but if we use dsymutil to generate .dSYM and DON'T have the<br class="">object files, this version of GDB can't give us full backtraces; we get<br class="">the function names only: no line numbers, no arguments, no ability to<br class="">access global variables, etc. Apparently it can't get full details from<br class="">the dSYM files. However, at least it does what little it does reliably.<br class=""><br class="">So we first tried to get the latest GDB with homebrew and use that, but<br class="">it simply does not work at all:<br class=""><br class=""> $ gdb -c core.78225 dist/bin/myprog<br class=""> GNU gdb (GDB) 7.8.1<br class=""> ..<br class=""> "/Users/build/crash/core.78225": no core file handler recognizes format<br class=""><br class="">Building GDB myself from source gives the same result. So, we turned to<br class="">LLDB to try to get the same behavior... and it just does not work<br class="">reliably.<br class=""><br class="">First, is there any sort of comprehensive manual for the LLDB CLI? On<br class=""><a href="http://lldb.llvm.org" class="">lldb.llvm.org</a> I see a tutorial and a command comparison with GDB, but<br class="">nowhere can I find any sort of manual akin to the GDB manual that<br class="">describes all the LLDB CLI commands, what they do, etc... ?<br class=""><br class="">We tried to use the LLDB -s option to provide a script file; very<br class="">simple:<br class=""><br class=""> $ cat show.lldb<br class=""> target create --core core.78225 dist/bin/myprog<br class=""> thread backtrace all<br class=""> exit<br class=""><br class="">Now, with some core files this works just fine. However with other<br class="">cores, it fails completely:<br class=""><br class=""> $ lldb --version<br class=""> lldb-310.2.37<br class=""><br class=""> $ lldb -s show.lldb<br class=""> ..<br class=""> (lldb) thread backtrace all<br class=""> error: Aborting reading of commands after command #1: 'thread backtrace all' failed with error: invalid thread<br class=""> Aborting after_file command execution, command file: 'show.lldb' failed.<br class=""><br class="">If I do it interactively, exact same commands, exact same core, etc.<br class="">rather than via -s then it works every time. But using -s it fails (for<br class="">some cores), every time. Using "-o" multiple times to pass individual<br class="">commands instead of "-s" fails the same way.<br class=""><br class="">Even more frustrating is that when we get the above error, LLDB stops<br class="">processing the script file and SITS AT THE PROMPT because it never<br class="">processes the "exit" command!! This means our entire test suite hangs<br class="">right there. Redirecting stdin from /dev/null doesn't fix this; it's<br class="">even worse (it prints out 100's of "quit" commands then hangs).<br class="">Obviously not acceptable. There doesn't seem to be any LLDB equivalent<br class="">of GDB's "-batch" flag.<br class=""><br class=""><br class="">So then we gave up on the LLDB front-end and tried to write a Python<br class="">script to do the debugging that we want. Even though we just want to<br class="">run a couple of simple commands, this took some effort for my colleague<br class="">to learn the Python API and ended up with 160 lines of Python, but he<br class="">got it working.<br class=""><br class="">Sometimes it works, I should say.<br class=""><br class="">Other times, Python itself aborts ("Abort trap: 6"). Even this is not<br class="">so bad, because we can just put the invocation of Python into a loop and<br class="">eventually it usually works (unlike the -s option to lldb above, this<br class="">one doesn't depend on the core file; the same core file will sometimes<br class="">have Python dump core and sometimes not).<br class=""><br class="">However, other times the Python script just hangs forever and never<br class="">finishes; again this means the entire automated test suite hangs in this<br class="">situation.<br class=""><br class=""><br class="">At this point I don't feel like we have any alternative except to tell<br class="">people that there's no support for this capability on OSX and they'll<br class="">just have to debug all the cores by hand interactively, and we can't do<br class="">any automated categorization of cores based on backtraces, etc.<br class=""><br class="">I'm checking the output OSX dumps into ~/Library/Logs/DiagnosticReports<br class="">which doesn't have everything we need but at least has a stack trace.<br class=""><br class="">_______________________________________________<br class="">lldb-dev mailing list<br class=""><a href="mailto:lldb-dev@cs.uiuc.edu" class="">lldb-dev@cs.uiuc.edu</a><br class="">http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev<br class=""></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Thanks,</div><div class=""><i class="">- Enrico</i><br class="">📩 egranata@<font color="#ff2600" class=""></font>.com ☎️ 27683</div><div class=""><br class=""></div></div></div></div></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>