https://llvm.org/bugs/show_bug.cgi?id=24764
Bug ID: 24764
Summary: Various C++ language features can't be debugged well
on Windows
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
S
The community's current plan of record is still to kill the autoconf build
but there is no definitive timeline on when it will be complete. But to
answer your question, yes it is across all projects.
>From the LLDB side, I don't know if anyone depends on having a working
autoconf build for produc
Can you change it to CMake instead of configure? I know that's not
what you want to hear, but the configure build is on its way out, so
you're going to have to do this at some point anyway.
Zachary, is the decision to drop autoconf across all projects or just
LLDB? The last time I proposed a cm
I took a look at the buildbots; it looks like another buildbot is failing with
the same issue – the debian bot,
http://lab.llvm.org:8011/builders/lldb-x86_64-debian-clang . It fails the
compile at the same place as the Hexagon Ubuntu bot, and it also uses configure.
Google has 2 Ubuntu 14.04
We have a chunk of tests that are marked xfail that pass right now on OS
X. I'll go through those in the near future.
I'm also seeing several tests consistently unexpectedly pass on Linux
x86_64 (Ubuntu 14.04) built with clang-3.6. I think at least some of them
fail with gcc-4.9, so they might n
On 9 September 2015 at 14:21, Ed Maste via lldb-dev
wrote:
> Also, are these tests passing on Linux?
The tests seem to be passing for linux as well.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-de
Two tests are currently decorated with a @unittest2.expectedFailure
referencing rdar tickets. These tests pass consistently for me on
FreeBSD. Can I ask the Apple folks to look at these tickets and put
details in a public PR if appropriate? Alternatively, shall I switch
the tests to expectedFailure
https://llvm.org/bugs/show_bug.cgi?id=24759
Bug ID: 24759
Summary: The example "Using the lldb.py module in python" is
not working on Linux
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
