Re: [lldb-dev] Question about -break-insert in lldb-mi

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) >

Re: [lldb-dev] Question about -break-insert in lldb-mi

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

Re: [lldb-dev] LLDB-MI from Eclipse hangs

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

Re: [lldb-dev] LLDB-MI from Eclipse hangs

> 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

Re: [lldb-dev] lock() fails on my lldb::Type

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

Re: [lldb-dev] LLDB-MI from Eclipse hangs

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: