[lldb-dev] LLDB targeting NetBSD-8.0

I'm moving my efforts of porting LLDB from NetBSD-7.0 to NetBSD-8.0. I decided that 7.0 isn't worth more effort since libstdc++ is already too old (no ) and it misses support for debug registers and useful ptrace(2) interfaces for a full-process instrumentation. I'm going to upgrade the LLVM+Clan

Re: [lldb-dev] Standalone build broken after r269332

On 14.05.2016 02:46, Eugene Zelenko via lldb-dev wrote: > But biggest problem remains is how to specify Clang source and build > directories, since llvm-config doesn't tells about them. The requirement of source-code of Clang+LLVM and build dirs of Clang and LLVM is no-go in a package-manager use-

[lldb-dev] Standalone build broken after r269332

Hi! I tried to build standalone LLDB after r269332 change in LLDBStandalone.cmake and encountered next problems: It implies that LLVM and Clang were built separately, but they could be built together, so next changes should be made as in previous version: - include("${LLVM_OBJ_ROOT}/lib${LLVM_

[lldb-dev] No C++ SB API for Watchpoint callbacks?

Please correct me if I have missed something critical here, but the C++ SB API does not seem to provide a way to set callbacks to run when a watchpoint is hit (while SBBreakpoint and the private Watchpoint class does offer this functionality). * Is this omission by design? * Is there another way t

[lldb-dev] How to use command regex in this situation?

Actually I posted a question in stackoverflow? Can any one give me some suggestion? Thanks___ lldb-dev mailing list lldb-dev@list

Re: [lldb-dev] Listing memory regions in lldb

On Intel processors, the best way to do this is probably going to be to walk the page directory (see Intel processor manuals). Assuming someone implements this command in lldb, I hope it can be done in such a way as to allow different implementations when one os/architecture has a better way of doi

Re: [lldb-dev] Listing memory regions in lldb

> > Interestingly when I've worked on Windows core dumps before I've seen that > MiniDump, with the right flags, will deliberately insert a region in the > middle of the memory ranges to represent the unmapped space, on 64 bit it's > quite a large section. Are you saying that's a bug in the minid

Re: [lldb-dev] Listing memory regions in lldb

I have experimented with the GetMemoryRegionInfo approach on the internal APIs already, it has some positives and negatives. - GetMemoryRegionInfo is unimplemented for Linux and Mac core dumps. That's not necessarily a bad thing as it could be implemented the "right" way. (As Jim said GetMemory