[lldb-dev] Running check-lldb
Jim Ingham via lldb-dev
lldb-dev at lists.llvm.org
Wed Apr 19 11:03:55 PDT 2017
> On Apr 19, 2017, at 7:37 AM, Pavel Labath via lldb-dev <lldb-dev at lists.llvm.org> wrote:
>
> It is on purpose, although whether that purpose is worthwhile is debatable...
>
> We chose to run release builds there so to align the bots closer to the binaries we release. Unfortunately, it does mean we run into situations like these...
>
We should be running at least some bots with asserts enabled to catch this sort of issue.
The reason we release lldb with asserts off is that at least historically llvm/clang would assert too aggressively, and crash the debugger in many cases where it would have survived just fine. If you crash a compile session that was at best going to present a compile error, that's not so bad. But having the debugger crash mid-session because an expression went a little sour is not acceptable...
Maybe that situation has changed over time, and we can re-assess this decision? Though the below indicates maybe not???
Jim
> In any case, I have now a patch up for fixing one of the crashers. The main one (assert during relocation processing) seems to be caused by a recent change in llvm. I am working towards identifying the cause, but that may take a while.
>
> Then we can hopefully have a look at failures on your machine.
>
>
> On 19 April 2017 at 14:28, Scott Smith <scott.smith at purestorage.com> wrote:
> Yeah I found the buildbot instance for lldb on Ubuntu 14.04, but it looks like it is only running release builds. Is that on purpose?
>
> On Wed, Apr 19, 2017 at 3:59 AM, Pavel Labath <labath at google.com> wrote:
> It looks like we are triggering an assert in llvm on a debug build. I'll try to track this down ASAP.
>
>
> On 18 April 2017 at 21:24, Scott Smith via lldb-dev <lldb-dev at lists.llvm.org> wrote:
> I'm trying to make sure some of my changes don't break lldb tests, but I'm having trouble getting a clean run even with a plain checkout. I've tried the latest head of master, as well as release_40. I'm running Ubuntu 16.04/amd64. I built with:
>
> cmake ../llvm -G Ninja -DCMAKE_BUILD_TYPE=Debug
> ninja lldb
> ninja check-lldb
>
> Compiler is gcc-5.4, though I've also tried with clang-4.0.
>
> Am I missing something obvious? Is there a docker image / vm image / known good environments that I can use to reproduce a clean test run (on something Linux-y - sorry, I don't have a Mac)?
>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>
>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
More information about the lldb-dev
mailing list