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

2016-05-16 Thread Eugene Zelenko via lldb-dev
Hi, Pavel! On Mon, May 16, 2016 at 3:04 AM, Pavel Labath wrote: > Hi Eugene, > > my thoughts on this are inline. > > At which stage does the build now fail for you (after applying the > fixes above)? Build failed at very beginning: source/lldb.cpp:19:10: fatal error:

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

2016-05-16 Thread Greg Clayton via lldb-dev
I am fine with adding new key/value pairs to each memory region so feel free to extend as needed as long as any missing keys ("memory_type == stack" for example) default to something sensible. Then each process plug-in can do what it can do and the process plug-ins will fill in as much info as

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

2016-05-16 Thread Greg Clayton via lldb-dev
We just haven't gotten to it yet. If you implement this, please do it like we do the breakpoints. Greg Clayton > On May 13, 2016, at 11:34 AM, Daniel Noland via lldb-dev > wrote: > > Please correct me if I have missed something critical here, but the C++ > SB API

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

2016-05-16 Thread Greg Clayton via lldb-dev
Regular expression commands are not multi-line commands. So your approach of doing: (lldb) command regex jspatch 's/(.+)/p (id)[JPEngine evaluateScript:@"%1"]/' won't work with: jspatch 'var a = 10 var b = 20 a = a + b' because this will get executed as: (lldb) jspatch 'var a = 10 (lldb) var

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

2016-05-16 Thread Jim Ingham via lldb-dev
> On May 13, 2016, at 9:13 AM, Zachary Turner wrote: > > 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

Re: [lldb-dev] Push work-in-progress plugin for Process NetBSD?

2016-05-16 Thread Jim Ingham via lldb-dev
Provided it builds everywhere and you are planning on continuing to work on it, I see no problems with putting this into the lldb tree. If there are any parts that touch common code, you might want to submit those first (in appropriate chunks) so that the people who are going to review it can

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

2016-05-16 Thread Howard Hellyer via lldb-dev
Apologies for the confusion, I don't mean either of those. This was working on a debug tool for the IBM JVM. When we added the MiniDumpWithFullMemoryInfo to our calls to MiniDumpWriteDump we found it inserted blank ranges to keep the regions in the MINIDUMP_MEMORY_INFO_LIST structure

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

2016-05-16 Thread Pavel Labath via lldb-dev
Hi Eugene, my thoughts on this are inline. On 14 May 2016 at 01:46, Eugene Zelenko via lldb-dev wrote: > 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