Re: [lldb-dev] Bug in CommandObjectFrameVariable::DoExecute()

On 11/18/16 3:55 PM, Zachary Turner via lldb-dev wrote: On line 708 of CommandObjectFrame.cpp, I'm looking at this code: options.SetRootValueObjectName(name_cstr); This code occurs inside the else block of an if/else. name_cstr is declared prior to the if/else block and initialized to

[lldb-dev] Code ownership resignation

Hi, as some of you likely already know I will be leaving Apple at the end of November This career change also means I will not be as involved in lldb as I have been in the past. It also means I don't believe I would be doing the best interest of the community by serving as a code owner. For

Re: [lldb-dev] Connecting to lldb-rpc-server

It is my understanding that this is not possible in the current architecture > On Oct 7, 2016, at 11:55 AM, Rex Fenley wrote: > > We expect to have a rich user experience as this tool progresses, using > Python to generate UI will limit our development process. It would be

Re: [lldb-dev] Connecting to lldb-rpc-server

I can see a couple of avenues for your use case: - you can write custom LLDB commands (obligatory reference: http://lldb.llvm.org/python-reference.html ) and have your users type these via the console instead of by clicking buttons - you could write

Re: [lldb-dev] Connecting to lldb-rpc-server

I am gonna echo Kate's question, but delve one level deeper Why do you want to send commands to LLDB from a different process? We have a bunch of different extension points in LLDB, so it's possible that what you're trying to do is actually already possible > On Oct 7, 2016, at 10:41 AM, Rex

Re: [lldb-dev] RFC: Break/Watchpoint refactor

> On Sep 27, 2016, at 1:09 PM, Daniel Austin Noland via lldb-dev > wrote: > > * Prefer explicitly deleted copy ctor / assignments over multiline macro > DISALLOW_COPY_AND_ASSIGN Why not just move DISALLOW_COPY_AND_ASSIGN over to using =delete ? That seems like a

Re: [lldb-dev] LLDB Evolution - Final Form

> On Sep 19, 2016, at 2:31 PM, Zachary Turner via lldb-dev > wrote: > > > > On Mon, Sep 19, 2016 at 2:20 PM Mehdi Amini > wrote: > > > I’m surprise by your aversion to assertions, what is your suggested >

Re: [lldb-dev] LLDB Evolution - Final Form

A few remarks > On Sep 19, 2016, at 1:18 PM, Zachary Turner via lldb-dev > wrote: > > Following up with Kate's post from a few weeks ago, I think the dust has > settled on the code reformat and it went over pretty smoothly for the most > part. So I thought it might

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

> On Sep 13, 2016, at 10:02 AM, Lei Kong via lldb-dev > wrote: > > I wrote a lldb type summary provider for wstring with 16bit wchar on Ubuntu > 16.04. > > Things work fine if I manually do the following in lldb: > > (lldb) script import mytypes > (lldb) type

Re: [lldb-dev] UnicodeDecodeError for serialize SBValue description

> On Apr 20, 2016, at 3:08 PM, Jeffrey Tan wrote: > > Hi Enrico, > > Instead of trying function-evaluation c_str(), I decided to decode the > information from fbstring_core fields. I got it working but have two > questions for it. > > type summary add -F

Re: [lldb-dev] UnicodeDecodeError for serialize SBValue description

> On Apr 7, 2016, at 9:51 AM, Jim Ingham wrote: > > I don't think Enrico was suggesting that we maintain a bunch of third party > data formatters in the lldb source base. That depends - if this std::string implementation is part of a publicly available STL

Re: [lldb-dev] UnicodeDecodeError for serialize SBValue description

This is kind of orthogonal to your problem, but the reason why you are not seeing the kind of simplified printing Greg is suggesting, is because your std::string doesn’t look like any of the kinds we recognize Specifically, LLDB data formatters work by matching against type names, and once

Re: [lldb-dev] [Bug 27020] New: "command alias r run" causes an assert

Ted, > I think this is fixed by r264096 > > Can you try and make sure it works for you? > >> On Mar 21, 2016, at 2:51 PM, Enrico Granata via lldb-dev >> <lldb-dev@lists.llvm.org <mailto:lldb-dev@lists.llvm.org>> wrote: >> >> >>>

Re: [lldb-dev] [Bug 27020] New: "command alias r run" causes an assert

Ted, I think this is fixed by r264096 Can you try and make sure it works for you? > On Mar 21, 2016, at 2:51 PM, Enrico Granata via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > >> On Mar 21, 2016, at 2:27 PM, via lldb-dev <lldb-dev@lists.llvm.org >> <ma

Re: [lldb-dev] [Bug 27020] New: "command alias r run" causes an assert

> On Mar 21, 2016, at 2:27 PM, via lldb-dev wrote: > > Bug ID27020 > Summary "command alias r run" causes an assert > Product lldb > Version unspecified > Hardware PC > OSWindows

Re: [lldb-dev] something just toasted the test suite on OS X

Should be reverted in 258791. Sent from my iPhone > On Jan 25, 2016, at 8:54 PM, Zachary Turner wrote: > > sorry, yea I stuck around for a while after that patch waiting for emails, > but nothing came through. Please revert in the meantime, I'll work on a fix > tomorrow.

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev > wrote: > > Hi, > If I have an SBValue for an object whose type has a formatter enabled for it, > is there a way to detect this via the Python API, and if so, request an > "unmodified" view of the object?

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 4:09 PM, Vadim Chugunov via lldb-dev > wrote: > > lldb-340.4.119 (OSX 10.11.3) > > On Mon, Jan 25, 2016 at 3:42 PM, Siva Chandra > wrote: > On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 4:04 PM, Vadim Chugunov wrote: > > > > On Mon, Jan 25, 2016 at 3:31 PM, Enrico Granata > wrote: > >> >> Whose IsSynthetic() is supposed to return True,- the parent's or the >> child's? > > What do

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 4:48 PM, Siva Chandra wrote: > > I think this one: > http://llvm.org/viewvc/llvm-project?view=revision=240578 > > > On Mon, Jan 25, 2016 at 4:34 PM, Enrico Granata

Re: [lldb-dev] something just toasted the test suite on OS X

> On Jan 25, 2016, at 6:48 PM, Todd Fiala via lldb-dev > wrote: > > Not sure exactly what it is, but all the tests are failing due to some bad > assumptions of unicode vs. str on Python 2 vs. 3 if I had to guess. > Author: zturner Date: Mon Jan 25 18:59:42 2016 New

Re: [lldb-dev] Benchmark tests

Historically I would do $ ./dotest.py +b but I am not strongly attached to that workflow - it's just what I learnt the first time I needed to run one Sent from my iPhone > On Dec 9, 2015, at 2:08 PM, Zachary Turner wrote: > > When you do run the benchmark tests, what

Re: [lldb-dev] [Lldb-commits] [lldb] r253317 - Add Pythonic language binding wrapper generation script.

> On Nov 18, 2015, at 10:34 AM, Zachary Turner via lldb-dev > wrote: > > > > On Wed, Nov 18, 2015 at 10:00 AM Todd Fiala > wrote: > Checking in the static bindings is no different than projects checking in >