Re: [lldb-dev] Inquiry for performance monitors

2017-06-19 Thread Abhishek Aggarwal via lldb-dev
Hi Everyone I have developed a tool that facilitates lldb users using Intel(R) Processor Trace technology for debugging applications (as per discussions in this thread). The patch is https://reviews.llvm.org/D33035. Some highlights of this tool are: 1. The tool is built on top of lldb. It is not

Re: [lldb-dev] Inquiry for performance monitors

2016-02-05 Thread Abhishek Aggarwal via lldb-dev
Hi Greg Please find any answers/queries inlined: On Thu, Feb 4, 2016 at 9:58 PM, Greg Clayton via lldb-dev < lldb-dev@lists.llvm.org> wrote: > >> On Feb 4, 2016, at 2:24 AM, Pavel Labath via lldb-dev < lldb-dev@lists.llvm.org> wrote: >> >> On 4 February 2016 at 10:04, Ravitheja Addepally >>

Re: [lldb-dev] Inquiry for performance monitors

2016-02-04 Thread Abhishek Aggarwal via lldb-dev
Hello Pavel As per my understanding, instead of doing it by expression evaluation if the code (to enable pt and gathering the raw traces) is written on lldb-server side, then also lldb-server will have to wait for the inferior to stop in order to encapsulate all the traces in packets and send

Re: [lldb-dev] Inquiry for performance monitors

2016-02-04 Thread Pavel Labath via lldb-dev
On 4 February 2016 at 12:49, Abhishek Aggarwal wrote: > Hello Pavel > > As per my understanding, instead of doing it by expression evaluation > if the code (to enable pt and gathering the raw traces) is written on > lldb-server side, then also lldb-server will have to wait

Re: [lldb-dev] Inquiry for performance monitors

2016-02-01 Thread Pavel Labath via lldb-dev
Speaking for Android Studio, I think that we *could* use a python-based implementation (hard to say exactly without knowing the details of the implementation), but I believe a different implementation could be *easier* to integrate. Plus, if the solution integrates more closely with lldb, we could

Re: [lldb-dev] Inquiry for performance monitors

2016-02-01 Thread Tamas Berghammer via lldb-dev
If you want to go with the path to implement it outside LLDB then I would suggest to implement it with an out of tree plugin written in C++. You can use the SB API the same way as you can from python and additionally it have a few advantages: * You have a C/C++ API what makes it easy to integrate

Re: [lldb-dev] Inquiry for performance monitors

2016-01-21 Thread Ravitheja Addepally via lldb-dev
Hello, Regarding the questions in this thread please find the answers -> How are you going to present this information to the user? (I know debugserver can report some performance data... Have you looked into how that works? Do you plan to reuse some parts of that infrastructure?) and How

Re: [lldb-dev] Inquiry for performance monitors

2015-10-21 Thread Greg Clayton via lldb-dev
one main benefit to doing this externally is allow this to be done remotely over any debugger connection. If you can run expressions to enable/disable/setup the memory buffer/access the buffer contents, then you don't need to add code into the debugger to actually do this. Greg > On Oct 21,