Then the question becomes how can we identify the STL that is being used
correctly so we can do the right thing. I worry that if std::unique_ptr isn't
working that many many other STL things won't work as well. We are tuned for a
specific STL
> On Feb 27, 2018, at 2:12 PM, Pavel Labath via lldb
This probably isn't arch-dependent. More likely you just have a
different version of libstdc++. Can you share how the std::unique_ptr
layout looks like for you. This is how my std::unique_ptr looks like
(from libstdc++.so.6.0.22):
(lldb) fr var X -R -T
(std::unique_ptr >) X = {
(std::unique_ptr
It depends on the version of the C++ standard library you are using. Is this
the only thing that isn't working in the STL data formatters? I would expect
the STL library to be the same on PowerPC as it is on other platforms so I
wouldn't guess this would be an issue that is arch dependent.
Greg
Hi,
No major issues seen so far for mips. Binaries uploaded.
SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)=
6e4fab79cc341a9084dab94cced108daff39fcde14a11e8d7ae454e9f92cb77c
SHA256(clang+llvm-6.0.0-rc3-mips-linux-gnu.tar.xz)=
54887a039d3d7ccff17a0c7245f4c9d778a1c22f96b619db554849da55293d6
Hi,
LLDB is printing a empty value for unique pointers in PowerPC.
And I am investigating a solution for this problem.
The problem occurs because the ptr_obj variable has a empty value in
Plugins/Language/CPlusPlus/LibStdcppUniquePointer.cpp:73.
I could solve it, changing this line
Plugins/Lan
I only briefly scanned the patch, but I'm not sure treating D as another
mangling variant of C++ is the best model - I think it will be easier if we
gather all the separate language features up in the individual languages. You
might have a look at the swift-enabled lldb
(https://github.com/app
On 26 February 2018 at 19:32, Ed Maste via lldb-dev
wrote:
> 5. I copied the scripts (updateScripts.sh, checkoutSource.sh, etc.)
> from the previous buildbot installation (into scratch/scripts/). I
> think we should host all scripts for the builders in either the lldb
> or zorg repo - is there a r
On 26 February 2018 at 22:32, Ed Maste wrote:
>
> 2. Install required packages:
> # pkg install cmake ninja swig30 subversion py27-pip
Also gmake and bash.
> The host is running a FreeBSD 12-CURRENT kernel and to enable tests I
> expect I'll create a new FreeBSD 12 builder, which can be initiall
W dniu pią, 23.02.2018 o godzinie 16∶14 +0100, użytkownik Hans Wennborg
via Release-testers napisał:
> Dear testers,
>
> 6.0.0-rc3 was just tagged, after r325901 on the branch.
>
> There are still a few open blockers, but I'm not sure we'll actually
> end up blocking on all of them. So depending
https://bugs.llvm.org/show_bug.cgi?id=36540
Bug ID: 36540
Summary: "error: this file does not represent a loadable dylib"
when loading libsosplugin.so plugin from Python
Product: lldb
Version: 4.0
Hardware: PC
On Fri, Feb 23, 2018 at 4:14 PM, Hans Wennborg wrote:
> Dear testers,
>
> 6.0.0-rc3 was just tagged, after r325901 on the branch.
>
> There are still a few open blockers, but I'm not sure we'll actually
> end up blocking on all of them. So depending on what comes up, this
> release candidate is pr
https://bugs.llvm.org/show_bug.cgi?id=36538
Bug ID: 36538
Summary: Odd 'watchpoint set' errors on Android target
Product: lldb
Version: 6.0
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
https://bugs.llvm.org/show_bug.cgi?id=36534
Bug ID: 36534
Summary: SIGSEGV on 'image dump symfile'
Product: lldb
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
13 matches
Mail list logo
