Re: [lldb-dev] Selectively disabling value formatter

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

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Siva Chandra via lldb-dev
I think this one: http://llvm.org/viewvc/llvm-project?view=revision&revision=240578 On Mon, Jan 25, 2016 at 4:34 PM, Enrico Granata wrote: > > On Jan 25, 2016, at 4:09 PM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > lldb-340.4.119 (OSX 10.11.3) > > On Mon, Jan 25, 2016 at

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> 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 via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wro

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> 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 you mean with this? > The model is that y

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Siva Chandra via lldb-dev
On Mon, Jan 25, 2016 at 4:09 PM, Vadim Chugunov wrote: > lldb-340.4.119 (OSX 10.11.3) I have no idea what that number means. May be Enrico can figure if that build has the fix or not. > 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

2016-01-25 Thread Vadim Chugunov via lldb-dev
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 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 A

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Siva Chandra via lldb-dev
On Mon, 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? > I've experimented with value.IsS

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> On Jan 25, 2016, at 3:20 PM, Vadim Chugunov wrote: > > On Mon, Jan 25, 2016 at 11:04 AM, Enrico Granata > wrote: > >> On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev >> mailto:lldb-dev@lists.llvm.org>> wrote: >> >> Hi, >> If I have an SBValue for an obj

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Vadim Chugunov via lldb-dev
On Mon, Jan 25, 2016 at 11:04 AM, Enrico Granata wrote: > > On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> 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

Re: [lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Enrico Granata via lldb-dev
> 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? There definitely is a way

[lldb-dev] Selectively disabling value formatter

2016-01-25 Thread Vadim Chugunov via lldb-dev
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? I've experimented with value.IsSynthetic() and value.GetNonSyntheticValue(), but the former seems to always retu