[lldb-dev] [Bug 26677] New: LLDB does not report Linux signal 35 (SIGRTMIN+1)

2016-02-19 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=26677 Bug ID: 26677 Summary: LLDB does not report Linux signal 35 (SIGRTMIN+1) Product: lldb Version: 3.8 Hardware: PC OS: Linux Status: NEW Severity: normal

Re: [lldb-dev] [cfe-dev] [3.8 Release] Release status

2016-02-19 Thread Quentin Colombet via lldb-dev
Hi Hans, > On Feb 19, 2016, at 9:55 AM, Quentin Colombet via cfe-dev > wrote: > > Hi Hans, > > Thanks for pushing this forward. > >> On Feb 18, 2016, at 4:22 PM, Hans Wennborg > > wrote: >> >> According to the schedule

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Quentin Colombet via lldb-dev
Hi Hans, Thanks for pushing this forward. > On Feb 18, 2016, at 4:22 PM, Hans Wennborg wrote: > > According to the schedule (e.g. on the right on llvm.org), we should > have tagged the release by now, but we haven't, so we're officially > behind schedule. I'm still

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Daniel Sanders via lldb-dev
I've changed the lit arguments to '-v' on my old 3.7.1 build and re-run check-all. I can confirm that these failures aren't regressions since LLVM 3.7.1 did not actually run any libc++ tests. Looking through the generated makefiles it seems that check-libcxx wasn't part of check-all.

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Renato Golin via lldb-dev
On 19 February 2016 at 00:22, Hans Wennborg via lldb-dev wrote: > - PR26600: Loop vectorization creates an unsafe out-of-bounds load > There's a patch out: http://reviews.llvm.org/D17332 > But no comments yet.. Hal? This looks like a serious bug but Hal's idea is

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Daniel Sanders via lldb-dev
Hi Hans, I think PR26369 should be on the list but we could potentially make do without it (see below). Without it we get 23 failures on libcxx tests caused by failing to link the tests with libatomic but libcxx itself is fine. One thing that's unclear is whether these failures are really

Re: [lldb-dev] problem with quoted strings in setting target.run-args

2016-02-19 Thread Pavel Labath via lldb-dev
Hi Ted, I did some improvements in this area a year ago, which (I hope) made things better, but they are still not perfect (hint: try running: settings set target.run-args '"') [that's ]. I tried to finish the job, but it ended up being too complicated, for the reasons you mention above... I

Re: [lldb-dev] Details on rdar://18684408?

2016-02-19 Thread Pavel Labath via lldb-dev
Linux is ok as well. I've enabled the tests everywhere except windows. Please add your arch back if you notice problems. pl On 18 February 2016 at 19:37, Zachary Turner via lldb-dev wrote: > Does not work on Windows yet, so please leave it xfail'ed on windows for now >