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
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
>>
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
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
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
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
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
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,