[lldb-dev] [Bug 32553] New: TestDataFormatterLibcxxVBool is flakey on Linux & Android

2017-04-06 Thread via lldb-dev
http://bugs.llvm.org/show_bug.cgi?id=32553 Bug ID: 32553 Summary: TestDataFormatterLibcxxVBool is flakey on Linux & Android Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW

Re: [lldb-dev] Was this an unintended consequence of the Args switch to StringRef's?

2017-04-06 Thread Jim Ingham via lldb-dev
If you can get that in, that would be great! Jim > On Apr 6, 2017, at 10:27 AM, Zachary Turner wrote: > > Honestly i think it seems reasonable for getAsInteger to just work in this > case, so I'll try to add it to llvm > On Thu, Apr 6, 2017 at 10:15 AM Jim Ingham wrote: > BTW, Jason says that

Re: [lldb-dev] Was this an unintended consequence of the Args switch to StringRef's?

2017-04-06 Thread Zachary Turner via lldb-dev
Honestly i think it seems reasonable for getAsInteger to just work in this case, so I'll try to add it to llvm On Thu, Apr 6, 2017 at 10:15 AM Jim Ingham wrote: > BTW, Jason says that sometimes the gdb remote protocol does send 0x > prefaced numbers. Apparently not in the cases which have been c

Re: [lldb-dev] Was this an unintended consequence of the Args switch to StringRef's?

2017-04-06 Thread Jim Ingham via lldb-dev
BTW, Jason says that sometimes the gdb remote protocol does send 0x prefaced numbers. Apparently not in the cases which have been changed to use getAsInteger with a radix of 16, but that is something we'll have to keep in mind. Jim > On Apr 5, 2017, at 6:55 PM, Jim Ingham wrote: > > base of

[lldb-dev] [Bug 32549] New: Code not executed when using "n"

2017-04-06 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=32549 Bug ID: 32549 Summary: Code not executed when using "n" Product: lldb Version: 3.3 Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal Priorit