Re: [lldb-dev] [cfe-dev] [6.0.0 Release] Release Candidate 1 tagged

2018-01-18 Thread Dimitry Andric via lldb-dev
On 17 Jan 2018, at 18:53, Hans Wennborg via cfe-dev wrote: > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. For an overview of what failed in the

[lldb-dev] Apple LLDB 900.0.64 crash

2018-01-18 Thread Johan Øverbye via lldb-dev
Hi :) I hope this is an appropriate use of this mailing list, my apologies if not. I couldn't find any form to report LLDB bugs and wasn't sure where to ask. With a recent update of Xcode I started getting an LLDB crash frequently while attempting to debug. (Not sure exactly which Xcode

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

2018-01-18 Thread Dimitry Andric via lldb-dev
On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers wrote: > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. Please run the test >

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

2018-01-18 Thread Brian Cain via lldb-dev
Uploaded afeb7f66eedd4d576ba8df9b4a551bb1908186e6 clang+llvm-6.0.0-rc1-linux-x86_64-sles11.3.tar.xz On Wed, Jan 17, 2018 at 11:53 AM, Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Dear testers, > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there

Re: [lldb-dev] [llvm-dev] Adding DWARF5 accelerator table support to llvm

2018-01-18 Thread Pavel Labath via lldb-dev
Thank you for all the responses. Unfortunately I wasn't able to make any progress on creating the patches today. I'll be sure to add everyone who expressed interest here to the phabricator diff once I have them ready. Jonas, do you have any dsymutil patches I can look at? I am interested in

Re: [lldb-dev] Questions about the LLDB testsuite and improving its reliability

2018-01-18 Thread Adrian Prantl via lldb-dev
> On Jan 18, 2018, at 5:07 AM, Pavel Labath wrote: > > Looks like I missed a party. :) > > I'll try to give my thoughts on some of the things that were said here: > >> make -C > I don't think make -C does what you think it does. "make -C foo" is > basically equivalent to

Re: [lldb-dev] [llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

2018-01-18 Thread Dimitry Andric via lldb-dev
On 18 Jan 2018, at 15:03, Jonas Hahnfeld wrote: > > Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >> wrote: >>> Start your engines; 6.0.0-rc1 was just tagged. >>> I know

Re: [lldb-dev] Questions about the LLDB testsuite and improving its reliability

2018-01-18 Thread Pavel Labath via lldb-dev
On 18 January 2018 at 17:52, Adrian Prantl wrote: > > >> On Jan 18, 2018, at 5:07 AM, Pavel Labath wrote: >> >> Looks like I missed a party. :) >> >> I'll try to give my thoughts on some of the things that were said here: >> >>> make -C >> I don't think make

Re: [lldb-dev] Apple LLDB 900.0.64 crash

2018-01-18 Thread Dimitry Andric via lldb-dev
Hi Johan, If it is Apple specific, create a report on the Apple Bug Reporter, at https://bugreport.apple.com/ . If you can reproduce the error with stock lldb, please report it on the LLVM bugtracker, at https://bugs.llvm.org/enter_bug.cgi

Re: [lldb-dev] Apple LLDB 900.0.64 crash

2018-01-18 Thread Greg Clayton via lldb-dev
This is a crash that is happening as we are trying to translate DWARF back into Clang ASTs. You can enable DWARF logging by doing: (lldb) log enable -f /tmp/dwarf.log dwarf info Or add that line to your ~/.lldbinit file. Then make it crash and we will have a log of what was wrong and might

Re: [lldb-dev] Questions about the LLDB testsuite and improving its reliability

2018-01-18 Thread Pavel Labath via lldb-dev
Looks like I missed a party. :) I'll try to give my thoughts on some of the things that were said here: > make -C I don't think make -C does what you think it does. "make -C foo" is basically equivalent to "cd foo && make", which is what we are doing now already. Of course, you can make this

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

2018-01-18 Thread Dimitry Andric via lldb-dev
On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers wrote: > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. Please run the test >

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

2018-01-18 Thread Michał Górny via lldb-dev
W dniu śro, 17.01.2018 o godzinie 18∶53 +0100, użytkownik Hans Wennborg via Release-testers napisał: > Dear testers, > > Start your engines; 6.0.0-rc1 was just tagged. > > I know there are still open blockers and it's early in the process in > a way, but I'd like to find out where we are. Please

Re: [lldb-dev] Questions about the LLDB testsuite and improving its reliability

2018-01-18 Thread Adrian Prantl via lldb-dev
> On Jan 18, 2018, at 5:07 AM, Pavel Labath wrote: > > Looks like I missed a party. :) > > I'll try to give my thoughts on some of the things that were said here: > >> make -C > I don't think make -C does what you think it does. "make -C foo" is > basically equivalent to

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

2018-01-18 Thread Diana Picus via lldb-dev
Hi, Uploaded ARM & AArch64: b84b25397a4ea479d08c056b20582fd0a8e16bb6 clang+llvm-6.0.0-rc1-aarch64-linux-gnu.tar.xz c19100cf7fb1d0fea80ed3e761bfd293e807b59a clang+llvm-6.0.0-rc1-armv7a-linux-gnueabihf.tar.xz I am seeing some failures in compiler-rt (ARM, AArch64) and libcxx (just ARM), for which

[lldb-dev] [Bug 35991] [lldb] Please backport LLDB test regression fixes to 6.0 branch

2018-01-18 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=35991 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED