Re: [lldb-dev] lldb type summary provider - SBProcess is invalid

2016-09-15 Thread Greg Clayton via lldb-dev
When using the "script" command, lldb.process/thread/frame are always setup so you can use them _in_your_text_, but you probably shouldn't rely on them being setup inside your function. You should pass the process to it: (lldb) script myfile.func(lldb.process, args) Then you can use "myfile.fun

Re: [lldb-dev] lldb type summary provider - SBProcess is invalid

2016-09-15 Thread Jim Ingham via lldb-dev
Yes, the "script" command always sets up the lldb.{process/thread/frame} regardless of whether its input is one-line or from the Script Input reader. The help for script should specify that. Jim > On Sep 14, 2016, at 10:24 PM, Lei Kong via lldb-dev > wrote: > > Does the following qualify as

Re: [lldb-dev] [PATCH] D24591: [LIT] First pass of LLDB LIT support

2016-09-15 Thread Pavel Labath via lldb-dev
On 15 September 2016 at 16:15, Zachary Turner wrote: > lldb-commits to bcc, lldb-dev to cc. > >> The biggest feature I see missing here is the ability to run tests >> remotely. Remote debugging is the most important use case for our team, and >> now we have a number of (experimental) bots running

Re: [lldb-dev] Problem with watchpoints

2016-09-15 Thread Ted Woodward via lldb-dev
I found another issue, Daniel: GDBRemoteCommunicationClient::GetWatchpointSupportInfo calls SendPacketAndWaitForResponse, and assumes that a return of PacketResult::Success means that qWatchpointSupportInfo is handled by the remote server. That's not true; a null response also returns PacketRe

Re: [lldb-dev] [PATCH] D24591: [LIT] First pass of LLDB LIT support

2016-09-15 Thread Zachary Turner via lldb-dev
lldb-commits to bcc, lldb-dev to cc. > The biggest feature I see missing here is the ability to run tests remotely. Remote debugging is the most important use case for our team, and now we have a number of (experimental) bots running the remote test suite. We want to make sure we can debug correct