[lldb-dev] FYI: LLDB DWARF tests on Windows are broken

2018-02-06 Thread Adrian McCarthy via lldb-dev
It looks like tests of DWARF-specific functionality on Windows are failing because we're actually generating CodeView in a PDB rather than DWARF. For example, TestSignedTypes.py fails for reasons completely unrelated to whether the types are signed or not. Apparently DWARF and CodeView consider t

[lldb-dev] [Bug 36258] New: Include comprehensive list of all LLDB settings

2018-02-06 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=36258 Bug ID: 36258 Summary: Include comprehensive list of all LLDB settings Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement

Re: [lldb-dev] [RFC] Testsuite in lldb & possible future directions

2018-02-06 Thread Zachary Turner via lldb-dev
On Mon, Feb 5, 2018 at 8:12 PM Davide Italiano via lldb-dev < lldb-dev@lists.llvm.org> wrote: > > > Conclusions: > The reliability of the suite (and the health of the codebase) is very > important to us. If you have issues, let us know. > In general, I'm looking for any kind of feedback, feel free

Re: [lldb-dev] [RFC] Testsuite in lldb & possible future directions

2018-02-06 Thread Zachary Turner via lldb-dev
On Tue, Feb 6, 2018 at 8:19 AM Pavel Labath via lldb-dev < lldb-dev@lists.llvm.org> wrote: > On 6 February 2018 at 15:41, Davide Italiano > wrote: > > On Tue, Feb 6, 2018 at 7:09 AM, Pavel Labath wrote: > >> On 6 February 2018 at 04:11, Davide Italiano via lldb-dev > >> > >> So, I guess my quest

Re: [lldb-dev] [RFC] Testsuite in lldb & possible future directions

2018-02-06 Thread Davide Italiano via lldb-dev
On Tue, Feb 6, 2018 at 8:18 AM, Pavel Labath wrote: > On 6 February 2018 at 15:41, Davide Italiano wrote: >> On Tue, Feb 6, 2018 at 7:09 AM, Pavel Labath wrote: >>> On 6 February 2018 at 04:11, Davide Italiano via lldb-dev >>> >>> So, I guess my question is: are you guys looking into making sure

Re: [lldb-dev] [RFC] Testsuite in lldb & possible future directions

2018-02-06 Thread Pavel Labath via lldb-dev
On 6 February 2018 at 15:41, Davide Italiano wrote: > On Tue, Feb 6, 2018 at 7:09 AM, Pavel Labath wrote: >> On 6 February 2018 at 04:11, Davide Italiano via lldb-dev >> >> So, I guess my question is: are you guys looking into making sure that >> others are also able to reproduce the 0-fail+0-xpa

Re: [lldb-dev] [RFC] Testsuite in lldb & possible future directions

2018-02-06 Thread Davide Italiano via lldb-dev
On Tue, Feb 6, 2018 at 7:09 AM, Pavel Labath wrote: > On 6 February 2018 at 04:11, Davide Italiano via lldb-dev > wrote: >> Hi, >> in the last couple of months a lot of people put a lot of attentions >> and energy into lldb and we're starting to see the first results. I >> decided to sit down and

Re: [lldb-dev] [RFC] Testsuite in lldb & possible future directions

2018-02-06 Thread Davide Italiano via lldb-dev
On Tue, Feb 6, 2018 at 7:09 AM, Pavel Labath wrote: > On 6 February 2018 at 04:11, Davide Italiano via lldb-dev > wrote: >> Hi, >> in the last couple of months a lot of people put a lot of attentions >> and energy into lldb and we're starting to see the first results. I >> decided to sit down and

Re: [lldb-dev] [RFC] Testsuite in lldb & possible future directions

2018-02-06 Thread Pavel Labath via lldb-dev
On 6 February 2018 at 04:11, Davide Italiano via lldb-dev wrote: > Hi, > in the last couple of months a lot of people put a lot of attentions > and energy into lldb and we're starting to see the first results. I > decided to sit down and write this e-mail to state where we are and > what are some

[lldb-dev] [Bug 36251] New: Crash in "intern-state" thread after removing breakpoints and continue

2018-02-06 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=36251 Bug ID: 36251 Summary: Crash in "intern-state" thread after removing breakpoints and continue Product: lldb Version: 6.0 Hardware: PC OS: Linux Status:

[lldb-dev] Crash in "intern-state" thread after removing breakpoints and continue

2018-02-06 Thread Dmitry Antipov via lldb-dev
Hello, I'm facing the following 6.0.0-rc1 crash on Linux/X86: #0 0x70e027b6 in std::__uniq_ptr_impl >::_M_ptr (this=0x28) at /usr/include/c++/7/bits/unique_ptr.h:147 #1 0x70e01cbe in std::unique_ptr >::get (this=0x28) at /usr/include/c++/7/bits/unique_ptr.h:337 #2 0x7