enlight created this revision.
enlight added reviewers: ki.stfu, abidh.
enlight added a subscriber: LLDB.
enlight set the repository for this revision to rL LLVM.
While attempting to run lldb-mi on Windows it became apparent that it doesn't
consistently escape output, for instance error messages
tfiala added a comment.
Here's what you get with the same codebase, but using this cmake line instead:
cmake -GNinja ../llvm -DCMAKE_BUILD_TYPE=Debug
-DLLDB_EXPORT_ALL_SYMBOLS:BOOL=YES
bin/lldb
(lldb) log enable -S lldb process
(lldb) target create /bin/ls
Current executable set to
tfiala added a comment.
>> Could you elaborate on this?
>
> Sure, I'll see if I can reproduce the lack of backtrace symbol lookup that I
> was experiencing without exporting those symbols back in roughly Oct/Nov
> 2015. We've been using this flag ever since to address it.
>
>> I've been debug
tfiala added a comment.
In https://reviews.llvm.org/D26093#582825, @labath wrote:
> In https://reviews.llvm.org/D26093#582618, @tfiala wrote:
>
> > > If it unblocks something it might be ok, but it doesn't actually fix the
> > > problem.
> >
> > It allows debugging of lldb with lldb on Ubuntu.
labath added a comment.
In https://reviews.llvm.org/D26093#582618, @tfiala wrote:
> > If it unblocks something it might be ok, but it doesn't actually fix the
> > problem.
>
> It allows debugging of lldb with lldb on Ubuntu. This broke recently, and
> the CL here re-enables the ability to do t
