Re: [lldb-dev] [llvm-dev] [llvm-foundation] Sequential ID Git hook

I could see wanting to compare data from master and a release branch. If that means sequential IDs need to work across branches, then we're back to needing a fancier solution than 'rev-list –count'. --paulr From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of Chris Matthews via

Re: [lldb-dev] [llvm-dev] [llvm-foundation] Sequential ID Git hook

On 7 July 2016 at 17:56, Chris Matthews via llvm-dev wrote: > With both llvmlab and LNT, once you get to a range of IDs, it is needs to be > easy to find out what commits or commit range those IDs map to. Making no comment on how easy or hard it will actually be, doesn't it just have to be possib

Re: [lldb-dev] LLDB-MI from Eclipse hangs

Actually you should have seen a ^running as a response from -exec-continue: -exec-continue ^running (gdb) But we don't see that here. Also, -exec-continue doesn't believe it takes any arguments in the lldb-mi. Check the tools/lldb-mi/MICmdCmdExec.cpp source file in the LLDB sources. Note that

Re: [lldb-dev] LLDB-MI from Eclipse hangs

It looks like we continue and then ask fore thread groups? I am not sure on the rules of MI. Can you ask another question before receiving a response? If we say command 18 is "-exec-continue --thread-group i1", can you send command 19 without receiving a response? 314,372 18-exec-continue --thr

Re: [lldb-dev] Add support for OCaml native debugging

I understand your concern. I guess it could be possible to create a conditional test exercised on a particular condition (like the presence of the native compiler), and skipped otherwise. Is it possible for new files to trigger regressions? Most of the changes concern the language plugins, AST

Re: [lldb-dev] Add support for OCaml native debugging

I don't like the idea of not having tests. Promising tests and actually delivering on them are two entirely different things. And without them, we just end up with broken code and nobody to maintain it On Thu, Jul 7, 2016 at 6:23 AM Tamas Berghammer via lldb-dev < lldb-dev@lists.llvm.org> wrote: >

Re: [lldb-dev] Remote debugging - unix socket and/or specific port

Hi Pavel, Thanks for your answer! At least I know it’s not supposed to work as is. I’ll see if I can do something similar to what you guys did for Android platforms. Thanks again! Cheers, - Adrien Duermael > On Jun 29, 2016, at 5:07 AM, Pavel Labath wrote: > > Hi Adrien, > > I think yo

Re: [lldb-dev] LLDB-MI from Eclipse hangs

Thanks Greg for your reply. Attached below is the GDB trace, please let me know if it helps in any ways. It would be helpful if you can tell me on how to capture (I am really new to lldb, sorry for bothering you): - sample lldb-mi to see what it is doing. - complete packet log of the traffic betw

[lldb-dev] [Bug 28455] Thread state not in sync with process state

https://llvm.org/bugs/show_bug.cgi?id=28455 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[lldb-dev] [Bug 28455] New: Thread state not in sync with process state

https://llvm.org/bugs/show_bug.cgi?id=28455 Bug ID: 28455 Summary: Thread state not in sync with process state Product: lldb Version: 3.8 Hardware: PC OS: Windows NT Status: NEW Severity: normal

Re: [lldb-dev] Add support for OCaml native debugging

What type of binaries do you want to commit in? Generally we don't like putting binaries to the repository because they are not human readable so it is hard to review/diff them and they will only run on a single platform and a single architecture while we support a lot of different configuration.