That is my understanding of what the -f flag is supposed to do. It doesn't
take an argument, it just directs gdb to do "future-break" rather than "break".
The lldb MI should probably just parse & discard it.
Jim
> On Jul 11, 2016, at 1:59 PM, Pierson Lee (PIE)
> wrote:
>
> So the instance
So the instance I run into the error is setting a conditional breakpoint:
-break-insert -f -c "x==0" main.cpp:13
And I get:
MI: Error: Command Args. Validation failed. Args missing additional
information: f
^error,msg="Command 'break-insert'. Command Args. Validation failed. Args
missing addi
I wanted a log with Eclipse talking to lldb-mi to see if it was doing anything
odd. It's not:
-exec-continue --thread-group i1
< 5> send packet: $c#63
-list-thread-groups i1
We have lldb-mi launch hexagon-sim automatically; it launches the same way
debugserver does, with reverse-connect.
This is what Eclipse does when setting a breakpoint at main on a Hexagon
target, before -exec-run:
TX:21-break-insert -t -f main
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
-Original Me
If I don't specify the -f flag (with some random parameter), then a pending
breakpoint is not created and the initial binding fails. But if I specify the
-f with the random parameter, then it will bind when the library is loaded.
This is the behavior I see on gdb also, but sans the random parame
> On Jul 11, 2016, at 1:31 AM, dipt...@gmail.com wrote:
>
> Thanks Ted.
> Attached is the GDB log after enabling log while executing same commands
> manually from command prompt.
>
Is this the GDB log while still running lldb-mi? I would like to see a log of
any program that actually runs usi
When a class inherits from std::enable_shared_from_this, like Type does:
class Type :
public std::enable_shared_from_this,
public UserID
{
You must construct your object directly into a shared pointer right away so
that it can setup the std::weak_ptr (a member variable in the
std::ena
I'm not very familiar with Eclipse, so if there is a way to change start
sequence of MI commands, just remove "gdb-set target-async off" or replace
with "gdb-set target-async on". If not, then rebuild lldb-mi with
"disabled" target-async feature:
```
$ svn diff tools/lldb-mi/
Index: tools/lldb-mi/M
