[llvm-bugs] [Bug 34192] [5.0] check-lldb-unit hangs with lldb-server running

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Oct 20 15:40:46 PDT 2017


labath at google.com changed:

           What    |Removed                     |Added
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #8 from labath at google.com ---
(In reply to labath from comment #7)
> (In reply to Jonas Hahnfeld from comment #6)
> > (In reply to labath from comment #5)
> > > I believe <https://reviews.llvm.org/D39010> will fix your problem, but I
> > > can't tell for sure (as things were working for me in the first place). If
> > > you have some time, I'd appreciate it if you can test it.
> > 
> > I think this works, but maybe for the wrong reasons: I build with the LLVM
> > tree with Clang 4.0.1 and therefore have LD_LIBRARY_PATH with libc++ set. So
> > it does not pick up the newly built library in <root>/lib/...
> The purpose of the test is not to test the newly-built libc++. We just need
> _any_ c++ library around to be able to run the inferior. So, we pick the c++
> library that you build the rest of your toolchain with, since that has to be
> around and working. In your case, we just happen to need LD_LIBRARY_PATH set
> in order to use c++ library that we build with.
> So, unless I misunderstood something, I think this solution is fine.

I have committed r316244, which should fix this.

If the test still fails for you, or you think the fix is incorrect, let me

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20171020/e4f9b6e1/attachment.html>

More information about the llvm-bugs mailing list