[lldb-dev] [Bug 37950] ExecutionContext::GetByteOrder() always returns endian::InlHostByteOrder()

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=37950

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
 CC||jdevliegh...@apple.com

--- Comment #5 from Jonas Devlieghere  ---
Fixed in r368181

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


[lldb-dev] [Bug 42920] New: LLDB fails to evaluate expression with template class type

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=42920

Bug ID: 42920
   Summary: LLDB fails to evaluate expression with template class
type
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: sfunkenhau...@google.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

LLDB fails to evaluate expressions with template class types.

Simple example:
template  class foo
{ 
  uint32_t data;
};

foo test;

int main() {
  return 0;
}

I set a breakpoint on main and try to evaluate the following expression:
(lldb) p sizeof(foo)
error: implicit instantiation of undefined template 'foo'
template is declared here

The debug information is available (It's not being optimized out), and printing
'test' works just fine:
$ readelf --debug-dump a.out | grep foo
<41>   DW_AT_name: (indirect string, offset: 0xa): foo
<49>   DW_AT_name: (indirect string, offset: 0x0): foo
3f  foo

Quoting Jim Ingham from a discussion on lldb-dev@
"LLDB uses clang as its expression parser, which when it sees foo
apparently wants to find a decl called "foo" first, which we don't really have
in the abstract."

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


Re: [lldb-dev] [cfe-dev] [Release-testers] [9.0.0 Release] Release Candidate 1 is here

2019-08-07 Thread Dimitry Andric via lldb-dev
On 2019-08-06 22:59, Marshall Clow wrote:
> Many of the failing libc++ tests are explicitly XFAILed for NetBSD; I wonder 
> if they should also be for FreeBSD.

If they can't be fixed, then indeed they should be XFAILed.  But maybe not 
right away, see below.


>libcxx/thread/thread.threads/thread.thread.this/sleep_for.pass.cpp
>  I don't know about this one.

Apparently it slept for too long:

Assertion failed: (std::abs(ns.count()) < err.count()), function main, file 
/home/dim/llvm/9.0.0/rc1/llvm.src/projects/libcxx/test/libcxx/thread/thread.threads/thread.thread.this/sleep_for.pass.cpp,
 line 68.

Cause is unknown.


>   libc++ :: std/language.support/support.runtime/ctime.pass.cpp
> Does your C library have "timespec_get" ?

Yes, but it got introduced only in FreeBSD 12.0.  I ran the tests on FreeBSD 
11.3, where it got:

/home/dim/llvm/9.0.0/rc1/llvm.src/projects/libcxx/test/std/language.support/support.runtime/ctime.pass.cpp:25:2:
 error: TIME_UTC not defined

This could be worked around by checking the FreeBSD major version, using e.g. 
"#if __FreeBSD__ >= 12".


>   libc++ ::
>
> std/localization/locale.categories/category.collate/locale.collate.byname/compare.pass.cpp

For this particular test, FreeBSD, Linux and Windows seem to have a different 
opinion than macOS on the result of std::strcoll("aaA", "BaA"), when 
the locale is en_US.UTF-8:

* macOS 10.14 gives 31
* FreeBSD 13.0 gives -13
* Linux (Ubuntu 18.04) gives -1
* Windows 10 (VS 2017) gives -1

E.g. macOS, which the test appears to be based on, is the odd one out here. :)

I won't pretend to fully understand the Unicode collation rules, but it could 
be that macOS does a case insensitive comparison, while the other systems do a 
case sensitive comparison.


>   libc++ ::
>
> std/localization/locale.categories/category.collate/locale.collate.byname/transform.pass.cpp

This test failed because it segfaults on FreeBSD, due to a bug in our 
wcsxfrm_l(3). :-)

I have fixed the bug in FreeBSD 13 here: 
https://svnweb.freebsd.org/changeset/base/350697, but it may take a while 
before it is merged into FreeBSD 12 and 11.


> These contain:
> // NetBSD does not support LC_COLLATE at the moment
> // XFAIL: netbsd
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_fr_FR.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_ru_RU.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_zh_CN.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.money.put/locale.money.put.members/put_long_double_fr_FR.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.money.put/locale.money.put.members/put_long_double_ru_RU.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.money.put/locale.money.put.members/put_long_double_zh_CN.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/curr_symbol.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/grouping.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/neg_format.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/pos_format.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.monetary/locale.moneypunct.byname/thousands_sep.pass.cpp
> These contain:
> // NetBSD does not support LC_MONETARY at the moment
> // XFAIL: netbsd
>   libc++ ::
>
> std/localization/locale.categories/category.time/locale.time.get.byname/get_monthname.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.time/locale.time.get.byname/get_monthname_wide.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.time/locale.time.get.byname/get_one.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.time/locale.time.get.byname/get_one_wide.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/category.time/locale.time.put.byname/put1.pass.cpp
> These contain:
> // NetBSD does not support LC_TIME at the moment
> // XFAIL: netbsd
>   libc++ ::
>
> std/localization/locale.categories/facet.numpunct/locale.numpunct.byname/grouping.pass.cpp
>   libc++ ::
>
> std/localization/locale.categories/facet.numpunct/locale.numpunct.byname/thousands_sep.pass.cpp
> These contain:
> // NetBSD does not support LC_NUMERIC at the moment
> // XFAIL: netbsd
>   libc++ :: std/re/re.alg/r

[lldb-dev] [Bug 16183] LLDB finds incorrect python version if python 3 is installed (Arch Linux)

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=16183

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #2 from Jonas Devlieghere  ---
LLDB is now fully compatible with Python 2 and Python 3, as well as SWIG 2 and
later.

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


[lldb-dev] [Bug 25744] Linux build breaks when both python 2 and python 3 are installed

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=25744
Bug 25744 depends on bug 25866, which changed state.

Bug 25866 Summary: Gentoo Linux build breaks in some scenarios when both Python 
2 and Python 3 are present
https://bugs.llvm.org/show_bug.cgi?id=25866

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

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


[lldb-dev] [Bug 25866] Gentoo Linux build breaks in some scenarios when both Python 2 and Python 3 are present

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=25866

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
LLDB is now fully compatible with Python 2 and Python 3, as well as SWIG 2 and
later.

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


[lldb-dev] [Bug 20206] [PATCH] Install script for python wrapper does not honour DESTDIR

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=20206

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com
 Resolution|--- |FIXED

--- Comment #1 from Jonas Devlieghere  ---
This now all done by CMake.

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


[lldb-dev] [Bug 20258] Ensure test infrastructure picks up segfaults and other exceptional exits from python test process

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=20258

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com
 Resolution|--- |FIXED

--- Comment #3 from Jonas Devlieghere  ---
lit detects crashes and marks tests as unresolved.

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


[lldb-dev] [Bug 23785] Problem with lib64/python2.7 installation

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=23785

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #15 from Jonas Devlieghere  ---
We made a lot of changes to CMake with regards to Python. I'm fairly confident
we support all the scenarios now. Please REOPEN if this still happens.

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


[lldb-dev] [Bug 21747] -var-list-children for a varobject with numchild==0 should return empty list instead of the value "[]"

2019-08-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=21747

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi was moved to a downstream repository:
https://github.com/lldb-tools/lldb-mi

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