On Tue, Aug 16, 2016 at 11:06 AM, Jim Ingham wrote:
>
> > On Aug 16, 2016, at 10:42 AM, Benjamin Dicken <
> bddic...@datawareventures.com> wrote:
> >
> > Thanks for the quick reply.
> >
> > > Are you sure the actual handling of the breakpoint & callback in lldb
> is what is taking most of the tim
> On Aug 15, 2016, at 4:59 PM, Lei Kong wrote:
>
> Should I use lldb::SBTarget::GetModuleAtIndex() to get all modules and then
> lldb::SBModule::GetSymbolAtIndex() to go through all symbols?
> Thanks.
This is the only way right now as we don't have a SBModule::FindSymbols that
takes a regular
> On Aug 16, 2016, at 10:42 AM, Benjamin Dicken
> wrote:
>
> Thanks for the quick reply.
>
> > Are you sure the actual handling of the breakpoint & callback in lldb is
> > what is taking most of the time?
>
> I'm not positive. I did collect some callgrind profiles to take a look at
> where
Thanks for the quick reply.
> Are you sure the actual handling of the breakpoint & callback in lldb is
what is taking most of the time?
I'm not positive. I did collect some callgrind profiles to take a look at
where most of the time is being spent, but i'm not very familiar with lldb
internals so
Hi Ravitheja,
Could you show us the diff to your cmake configuration? You may want to take a
look at how the LLVM_BUILD_INSTRUMENTED cmake option is implemented to
double-check that you've got something reasonable (see: llvm/CMakeLists.txt and
cmake/modules/HandleLLVMOptions.cmake).
Also, you may
Are you sure the actual handling of the breakpoint & callback in lldb is what
is taking most of the time? The last time we looked at this, the majority of
the work was in communicating with debugserver to get the stop notification and
restart. Note, besides all the packet code, this involves c
I recently started using lldb to write a basic instrumentation tool for
tracking the values of variables at various code-points in a program. I've
been working with lldb for less than two weeks, so I am pretty new. Though,
I have used and written llvm passes in the past, so I'm familiar with the
cl
Hello,
I was trying to get Code Coverage for LLDB with GCOV on Linux by
adding the corresponding flags in the CMake files, but I am facing problem
with lldb-server, which does not give seem to generate the gcda files. The
host side does generate the gcov files although. The lldb-server does
