It looks like `lldbsuite.lldb_root` is not getting set correctly for you.
Line 1070 of lldbsuite/test/dotest.py looks like this:
lldbRootDirectory = lldbsuite.lldb_root
`lldbsuite.lldb_root` is set in `packages/Python/lldbsuite/__init__.py`
whenever someone writes `import lldbsuite`. The imp
Can you give me a stack trace?
On Wed, Oct 28, 2015 at 10:37 PM Zachary Turner wrote:
> Shoot, I'm at the LLVM Developers Conference tomorrow and Friday as well.
> Let me eyeball the code and see if I can figure out what might be wrong.
>
>
> On Wed, Oct 28, 2015 at 4:25 PM Greg Clayton wrote:
Shoot, I'm at the LLVM Developers Conference tomorrow and Friday as well.
Let me eyeball the code and see if I can figure out what might be wrong.
On Wed, Oct 28, 2015 at 4:25 PM Greg Clayton wrote:
> Zach: this no longer works:
>
> % ./dotest.py -A x86_64 -C clang -v -t
> /.../packages/Python/
Zach: this no longer works:
% ./dotest.py -A x86_64 -C clang -v -t
/.../packages/Python/lldbsuite/test/functionalities/completion
fill "..." in with your path to your lldb root.
It is unable to find lldb because lldbtest_config.lldbExec isn't set
correctly...
> On Oct 28, 2015, at 12:21 PM,
Hi all,
I've made a few changes to the Apple OS X buildbot today. These are mostly
minor, but the key is to make sure we all know when it's broken.
First off, it now builds the lldb-tool scheme using the Debug
configuration. (Previously it was building a BuildAndIntegration
configuration, which
The fix seems to work -
http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/7900
.
Thank you.
On Wed, Oct 28, 2015 at 12:21 PM, Zachary Turner wrote:
> Committed r251544 to try to fix this.
>
> On Wed, Oct 28, 2015 at 12:18 PM Zachary Turner
> wrote:
>
>> It's saying "import
Committed r251544 to try to fix this.
On Wed, Oct 28, 2015 at 12:18 PM Zachary Turner wrote:
> It's saying "import: command not found". Do I need to put a
> `#!/usr/bin/env python` or something at the top? I thought by virtue of
> having a .py extension this would be handled, but maybe not.
>
It's saying "import: command not found". Do I need to put a
`#!/usr/bin/env python` or something at the top? I thought by virtue of
having a .py extension this would be handled, but maybe not.
On Wed, Oct 28, 2015 at 12:16 PM Zachary Turner wrote:
> We can set executable permissions
> on packa
We can set executable permissions
on packages/Python/lldbsuite/test/dotest.py for now. I suppose that's
actually necessary for now since it does tget executed indirectly by dosep.
I plan to remove the need for this, and at the same time make it fail if
you try to run that file directly. Will tha
Linux build bot is failing
http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/7895
:
/lldb-buildbot/lldbSlave/buildWorkingDir/scripts/../llvm/tools/lldb/test/dotest.py
--executable
/lldb-buildbot/lldbSlave/buildWorkingDir/scripts/../build/bin/lldb -A i386
-C clang-3.5 -s logs-
https://llvm.org/bugs/show_bug.cgi?id=25338
Bug ID: 25338
Summary: vdso unwinding doesn't work properly on GCE
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
This is in right now (without my proposed change from previous email,
although I can make that as a followup since it's just cleanup)
In any case, let me know if anything blows up. It took 35 minutes just to
commit, so hopefully any problems that arise can be fixed with localized
patches instead
12 matches
Mail list logo
