[lldb-dev] [Bug 30492] On Linux, lldb lit tests fail

https://llvm.org/bugs/show_bug.cgi?id=30492 Hal Finkel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

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

Hi! I'm trying to connect to Xcode's lldb rpc server but I'm having trouble. This doesn't seem to work to list the hosts. rpcinfo -p lldb-rpc-server Can't contact rpcbind on lldb-rpc-server rpcinfo: RPC: Unknown host Am I doing this correctly? -- Rex Fenley | IOS DEVELOPER Remind.com

Re: [lldb-dev] fate of TimeValue

I see one usage of of chrono in the Fuzzer, and that's about it. On 6 October 2016 at 17:46, Zachary Turner wrote: > I'd love to move over to chrono. For Utility functions such as those you > propose probably we should consider whether they should go into llvm. Does > llvm currently use anything

Re: [lldb-dev] fate of TimeValue

I'd love to move over to chrono. For Utility functions such as those you propose probably we should consider whether they should go into llvm. Does llvm currently use anything from chrono or have any chrono support functions yet? On Thu, Oct 6, 2016 at 5:39 PM Pavel Labath via lldb-dev < lldb-dev@l

[lldb-dev] fate of TimeValue

Hello all, in line with the "deinventing the wheel" movement, I'd like to remove the TimeValue class from LLDB. I've done some research on a flight this week, and as far as I can tell all functionality can be easily replaced with appropriate usage of std::chrono::duration and time_point. The only

Re: [lldb-dev] Asserts in StringRef::front

Thanks for the heads up. I do run with asserts, so I'm not sure why I didn't see this particular failure. In any case i'll go back and look through my changes for any other occurrences of this. Most of the time args were being checked before being used. Like the code would go: const char *arg

[lldb-dev] Asserts in StringRef::front

I fixed a bug in CommandObject::Execute that cause test-suite crashes when running with an Assert build of llvm (r283479.) The test was doing: break modify -c '' which is the way you unset a condition on a breakpoint. So the StringRef for that option value was empty, and it appears that you a