Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot
I hit the same problem last week. I ended up blowing away my build directory, and the problem went away. Probably a cache issue, but I was unable to reproduce... On Tue, Nov 7, 2017 at 10:21 AM, Jim Ingham via lldb-dev < lldb-dev@lists.llvm.org> wrote: > The lldb_cmake GreenDragon bot is now failing, e.g.: > > http://lab.llvm.org:8080/green/view/LLDB/job/lldb_cmake/1703/consoleFull# > 589016626e9a0fee5-ebcc-4238-a641-c5aa112c323e > > This looks related to Pavel's change: > > > r316728 | labath | 2017-10-26 19:24:04 -0700 (Thu, 26 Oct 2017) | 18 > lines > > > > Default to using in-tree clang for building test executables > > > > Summary: > > Using the in-tree clang should be the default test configuration as that > > is the one compiler that we can be sure everyone has (better > > reproducibility of test results). Also, it should hopefully reduce the > > impact of pr35040. > > > > This also reduces the number of settings which control the compiler > > used. LLDB_TEST_C_COMPILER is used for C files and > > LLDB_TEST_CXX_COMPILER for C++ files. Both of the settings default to > > the in-tree clang. > > > > Reviewers: zturner > > > > Subscribers: mgorny, davide, lldb-commits > > > > Differential Revision: https://reviews.llvm.org/D39215 > > > > The error is: > > CMake Error at tools/lldb/CMakeLists.txt:78 (message): > > LLDB test compilers not specified. Tests will not run > > > Does the bot need to be reconfigured for these changes? > > Jim > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] What's the best way to use "--all-files" option from python?
Do you mean just pass a pattern to the -f option or FileSpec?
On Tue, Oct 24, 2017 at 6:50 PM, Zachary Turner <ztur...@google.com> wrote:
> It might be worth brainstorming if there’s ways to do this that are both
> intuitive and don’t require more options. As a command line user, I really
> value my keystrokes.
>
> One idea would be to use a syntax that matches that of the ‘-name’ option
> to the standard ‘find’ utility. This way filename pattern matching would
> work in a way familiar to almost everyone, no sb api options would need to
> be added.
>
>
>
> On Mon, Oct 23, 2017 at 6:25 PM Jim Ingham via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Yeah, that would be easy to implement from the command line, maybe add a
>> --file-is-regex flag or something.
>>
>> From the SB API it would be better to have something like:
>>
>> SBFileList SBTarget.GetFileListMatchingRegex("regex")
>>
>> Please file an enhancement request for these of hack'em in if you're so
>> motivated.
>>
>> Jim
>>
>>
>> > On Oct 23, 2017, at 6:13 PM, Don Hinton <hinto...@gmail.com> wrote:
>> >
>> > Ah, great, thanks. I just figured the default was the same for both.
>> >
>> > Just wish I could use a regex for the filename as well, which would cut
>> down the number of files about about half.
>> >
>> > thanks again...
>> > don
>> >
>> > On Mon, Oct 23, 2017 at 6:02 PM, Jim Ingham <jing...@apple.com> wrote:
>> > Just pass an invalid FileSpec for the source file spec, like:
>> >
>> > lldb.target.BreakpointCreateBySourceRegex("printf", lldb.SBFileSpec())
>> >
>> > and it acts the same way as the --all-files option. That was pretty
>> non-obvious, I'll update the docs.
>> >
>> > Actually, the thing you CAN'T do is get the command line behavior where
>> lldb uses the "default file" i.e. when you run "break set -p" but don't
>> supply a file or the --all-files option. That seemed to me less useful for
>> a programming interface since the default file is history dependent (it's
>> the file with "main" in it before you run, then it's where you last set a
>> breakpoint, or where you last stopped, etc.) If you needed this behavior
>> it would be better to have the target vend the default file, though right
>> now that's really only maintained by the breakpoint command...
>> >
>> > Jim
>> >
>> >
>> > > On Oct 23, 2017, at 5:31 PM, Don Hinton via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>> > >
>> > > The only way I've been able to do it is by using the
>> CommandInterpreter, i.e.,
>> > >
>> > > res = lldb.SBCommandReturnObject()
>> > > lldb.debugger.GetCommandInterpreter().HandleCommand('breakpoint
>> set -p "diag::%s" --all-files -N %s' % (name, name), res);
>> > > lldb.debugger.GetCommandInterpreter().HandleCommand('breakpoint
>> disable %s' % name, res);
>> > >
>> > > Is this the best way to do it? Can't seem to figure out how to use
>> SBTarget.BreakpointCreateBySourceRegex() for all files.
>> > >
>> > > thanks...
>> > > don
>> > > ___
>> > > lldb-dev mailing list
>> > > lldb-dev@lists.llvm.org
>> > > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>> >
>> >
>>
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] What's the best way to use "--all-files" option from python?
Ah, great, thanks. I just figured the default was the same for both.
Just wish I could use a regex for the filename as well, which would cut
down the number of files about about half.
thanks again...
don
On Mon, Oct 23, 2017 at 6:02 PM, Jim Ingham <jing...@apple.com> wrote:
> Just pass an invalid FileSpec for the source file spec, like:
>
> lldb.target.BreakpointCreateBySourceRegex("printf", lldb.SBFileSpec())
>
> and it acts the same way as the --all-files option. That was pretty
> non-obvious, I'll update the docs.
>
> Actually, the thing you CAN'T do is get the command line behavior where
> lldb uses the "default file" i.e. when you run "break set -p" but don't
> supply a file or the --all-files option. That seemed to me less useful for
> a programming interface since the default file is history dependent (it's
> the file with "main" in it before you run, then it's where you last set a
> breakpoint, or where you last stopped, etc.) If you needed this behavior
> it would be better to have the target vend the default file, though right
> now that's really only maintained by the breakpoint command...
>
> Jim
>
>
> > On Oct 23, 2017, at 5:31 PM, Don Hinton via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> > The only way I've been able to do it is by using the CommandInterpreter,
> i.e.,
> >
> > res = lldb.SBCommandReturnObject()
> > lldb.debugger.GetCommandInterpreter().HandleCommand('breakpoint set
> -p "diag::%s" --all-files -N %s' % (name, name), res);
> > lldb.debugger.GetCommandInterpreter().HandleCommand('breakpoint
> disable %s' % name, res);
> >
> > Is this the best way to do it? Can't seem to figure out how to use
> SBTarget.BreakpointCreateBySourceRegex() for all files.
> >
> > thanks...
> > don
> > ___
> > lldb-dev mailing list
> > lldb-dev@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] What's the best way to use "--all-files" option from python?
The only way I've been able to do it is by using the CommandInterpreter,
i.e.,
res = lldb.SBCommandReturnObject()
lldb.debugger.GetCommandInterpreter().HandleCommand('breakpoint set -p
"diag::%s" --all-files -N %s' % (name, name), res);
lldb.debugger.GetCommandInterpreter().HandleCommand('breakpoint disable
%s' % name, res);
Is this the best way to do it? Can't seem to figure out how to use
SBTarget.BreakpointCreateBySourceRegex() for all files.
thanks...
don
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
