Re: [lldb-dev] [Bug 34676] check-lldb target fails on Windows due to incomplete compiler path

[Carlos Alberto Enciso via lldb-dev]

Hi Adrian,

Thanks very much for sharing your results.

Carlos

On Tue, Sep 26, 2017 at 4:31 PM, Adrian McCarthy 
wrote:

> I haven't spent too much time in LLDB lately.  The number of failures you
> see seems a little high.  On Windows 7, I get:
>
> ===
> Test Result Summary
> ===
> Test Methods:   1301
> Reruns:   28
> Success: 387
> Expected Failure:237
> Failure:   4
> Error:11
> Exceptional Exit:  0
> Unexpected Success:3
> Skip:659
> Timeout:   0
> Expected Timeout:  0
>
>
> On Tue, Sep 26, 2017 at 5:31 AM, Carlos Alberto Enciso <
> international.phan...@gmail.com> wrote:
>
>> Hi Adrian,
>>
>> As you are working on the above Windows issue, I am assuming you are
>> running LLDB on Windows.
>> I have managed to build LLDB on Windows 10, after getting the correct
>> dependencies.
>>
>> But from the LLDB home page, it seems that LLDB is only built and no
>> tests are run:
>>
>>- LLDB Windows Server 2008 x86 (CMake, MSVS 2013, Windows SDK 8.1, no
>>tests) 
>>- LLDB Windows 7 x86 (CMake, MSVS 2013, Windows SDK 8.1, no tests)
>>
>>
>> I run the tests via 'check-lldb' and these are the results:
>>
>> 63>  ===
>>
>> 63>  Test Result Summary
>>
>> 63>  ===
>>
>> 63>  Test Methods:   1299
>>
>> 63>  Reruns:   68
>>
>> 63>  Success: 365
>>
>> 63>  Expected Failure:233
>>
>> *63>  Failure:  34*
>>
>> 63>CUSTOMBUILD : error : 14
>>
>> 63>  Exceptional Exit:  0
>>
>> *63>  Unexpected Success:5*
>>
>> 63>  Skip:648
>>
>> 63>  Timeout:   0
>>
>> 63>  Expected Timeout:  0
>>
>> I am wondering if these results match yours.
>>
>> Thanks very much,
>>
>> Carlos Enciso
>>
>> On Tue, Sep 19, 2017 at 11:08 PM, via lldb-dev 
>> wrote:
>>
>>> Adrian McCarthy  changed bug 34676
>>> 
>>> What Removed Added
>>> Assignee lldb-dev@lists.llvm.org amcca...@google.com
>>>
>>> *Comment # 1  on bug
>>> 34676  from Adrian McCarthy
>>>  *
>>>
>>> I'm starting with git bisect to see if I can pinpoint when this got broken. 
>>>  It
>>> looks like it may have been a while back already.
>>>
>>> --
>>> You are receiving this mail because:
>>>
>>>- You are the assignee for the bug.
>>>
>>>
>>> ___
>>> lldb-dev mailing list
>>> lldb-dev@lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>>
>>>
>>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 34758] New: r313904 causes "command source" to assert and die

[via lldb-dev]

https://bugs.llvm.org/show_bug.cgi?id=34758

Bug ID: 34758
   Summary: r313904 causes "command source" to assert and die
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: jing...@apple.com
CC: llvm-b...@lists.llvm.org

The assert in StartHandlingCommand trips (the value is eInProgress, should be
eIdle).

This also causes lldb to crash on startup if you have a .lldbinit, so I've
backed out the patchset for r313904 for now.

We apparently don't have any tests for command source (it was part of the
earliest bits of lldb from before we hired somebody to write the testsuite...)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] I had to back out r313904, it causes lldb to assert on startup if you have a .lldbinit file

[Jim Ingham via lldb-dev]

This actually asserts on any use "command source" is the one command that 
re-enters the command interpreter.  It should be as simple as getting command 
source to rest the state flag before it goes to do the sourcing.  I'll check 
that out tomorrow if nobody gets to it first.

command source is one of a set of early commands that we got into lldb before 
we had hired the person who wrote the testsuite way way back in the day, and 
though we went and backfilled the tests at that point, apparently we missed 
command source.  So we'll also have to add a test for that.

I also filed:

https://bugs.llvm.org/show_bug.cgi?id=34758

to cover the issue.

Jim

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev