It should work no matter where this type is. You will need to debug and find
out why it isn't being found as that is a bug.
> On Mar 16, 2018, at 12:19 AM, Florin Trofin via lldb-dev
> wrote:
>
> Hello,
>
> I have a custom Python formatter for my own string type (a specialization of
> std::b
> On Mar 14, 2018, at 8:22 PM, Florin Trofin via lldb-dev
> wrote:
>
> Hi,
>
> I came across the formatter example in unicode_strings.py where in
> utf16_summary() I see this code:
>
> string_data = value.process.ReadMemory(pointer, length, error)
> # utf8 is safe to emit as-is on OSX
> ret
Ok,but how do you debug this? Debugging the debugger's formatter seems
non-trivial. Are there any guides/steps?
Thanks!
F.
On Mon, Mar 19, 2018 at 10:29 AM, Greg Clayton wrote:
> It should work no matter where this type is. You will need to debug and
> find out why it isn't being found as that
On Mon, Mar 19, 2018 at 6:04 PM, Florin Trofin via lldb-dev
wrote:
> Ok,but how do you debug this? Debugging the debugger's formatter seems
> non-trivial. Are there any guides/steps?
>
I generally recommend enabling logs (through `log enable lldb
-f ~/somefile.txt`) and then work back from there
I've put a WIP patch up here: https://reviews.llvm.org/D44668
Sorry for the delay!
Erik
On 2018-01-26 3:56 PM, Greg Clayton wrote:
On Jan 26, 2018, at 8:38 AM, Erik Pilkington
mailto:erik.pilking...@gmail.com>> wrote:
On 2018-01-25 1:58 PM, Greg Clayton wrote:
On Jan 25, 2018, at 10:25 AM,
