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
> <[email protected]> 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
> [email protected]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
