Hi,
I’ve tried to build lldb from scratch for the first time and noticed the build
documentation is quite out-of-date.
http://lldb.llvm.org/build.html says to build the top-level Xcode project (with
Xcode4 no less!), which references files that do not exist.
docs/building-with-debug-llvm.txt re
>> - Using GetMemoryRegionInfo to iterate might be quite expensive if
there are many small memory regions.
>
> Remember that the other use for GetMemoryRegionInfo() might be a user
just asking about an address they have in a register or variable that is a
pointer. So if we do add a more complex
> On May 20, 2016, at 3:27 AM, Howard Hellyer wrote:
>
> >> - Using GetMemoryRegionInfo to iterate might be quite expensive if there
> >> are many small memory regions.
> >
> > Remember that the other use for GetMemoryRegionInfo() might be a user just
> > asking about an address they have in
Hi,
I am running into memory corruption in LLDB 3.8 release candidate on Linux
Ubuntu 15.10. I am trying to access stack frame and the symbol on this frame is
corrupted. Here is what I figured out:
"StackFrame" has field "m_sc" of type "SymbolContext""SymbolContext" has field
"symbol" which is "
Hi,
I am looking through LLDB code... Another dangerous operation is
Symtab::Finalize() that just swaps the array. This is especially bad since it
will defeat something like quick-and-dirty hack of preallocating a huge vector
upfront.
My first impulse to fix that (maybe just temporary to get me
> On May 20, 2016, at 3:15 PM, Eugene Birukov via lldb-dev
> wrote:
>
> Hi,
>
> I am looking through LLDB code... Another dangerous operation is
> Symtab::Finalize() that just swaps the array. This is especially bad since it
> will defeat something like quick-and-dirty hack of preallocating
