[lldb-dev] lldb status at windows

2016-01-06 Thread Red Skotina via lldb-dev
Where can i look lldb status for native debug at Windows? ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb status at windows

2016-01-07 Thread Red Skotina via lldb-dev
>> * Expression evaluation might not work in some advanced cases. >> >> The main big feature that has been added since the original blog post is >> support for windows minidump files. So you can create a minidump of a >> stopped process from inside LLDB, and you

[lldb-dev] LLDB build at windows

2016-01-09 Thread Red Skotina via lldb-dev
If i want compile as part of llvm then what is destination directory for lldb trunk sources ? I has placed this in llvm/projects/lldb and has much errors while compiling lldb with MSVC 2015. "d:\code\llvm\build\LLVM.sln" (целевой объект по умолчанию) (1) -> "d:\code\llvm\build\ALL_BUILD.vcxproj.m

Re: [lldb-dev] LLDB build at windows

2016-01-10 Thread Red Skotina via lldb-dev
t; |__ lld > |__ lldb > > You will need clang because lldb needs to link against it, and you will > need lld because lldb on Windows doesn't (yet) understand PDB, so you have > to compile your programs with clang.exe -fuse-ld=lld > > > > On Sat, Jan 9, 201

Re: [lldb-dev] LLDB build at windows

2016-01-11 Thread Red Skotina via lldb-dev
only >> empty directories. >> should i download something or should skip unittests ? >> >> 2016-01-10 6:28 GMT+03:00 Zachary Turner : >> >>> Should look like this: >>> >>> llvm >>> |__ tools >>> |__ clang >>&g

Re: [lldb-dev] LLDB build at windows

2016-01-11 Thread Red Skotina via lldb-dev
;>>> LINK : fatal error LNK1181: cannot open input file 'gtest.lib' >>>> [d:\code\llvm\ >>>> build\tools\lldb\unittests\Utility\UtilityTests.vcxproj] >>>> >>>> my commands: >>>> >>>> cmake -G "Visual Stu

Re: [lldb-dev] lldb status at windows

2016-01-22 Thread Red Skotina via lldb-dev
le in certain scenarios >>> * Conditional breakpoints don't work >>> * Hardware watchpoints don't work >>> * Expression evaluation might not work in some advanced cases. >>> >>> The main big feature that has been added since the original blog post

Re: [lldb-dev] lldb status at windows

2016-01-22 Thread Red Skotina via lldb-dev
atus on the website. Here's my best estimate at what you can expect. >>>>> >>>>> * Most common debugging scenarios should work. Run under debugger, >>>>> attach to process, interrupt, continue, print variable values, evaluate >>>>> e

Re: [lldb-dev] lldb status at windows

2016-01-23 Thread Red Skotina via lldb-dev
ina : >>>> >>>>> Nice to hear. I should answer after some time of using >>>>> >>>>> 2016-01-07 21:04 GMT+03:00 Zachary Turner : >>>>> >>>>>> Feel free to file bugs or post your feedback here after you use ab

Re: [lldb-dev] lldb status at windows

2016-01-23 Thread Red Skotina via lldb-dev
argv) >>>>>> { >>>>>> printf("hello1\n"); >>>>>> printf("hello2\n"); >>>>>> return 0; >>>>>> } >>>>>> >>>>>> d:\code\test

Re: [lldb-dev] lldb status at windows

2016-01-23 Thread Red Skotina via lldb-dev
>> >>>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina >>>>>>> wrote: >>>>>>> >>>>>>>> Look like I miss something , but i cant debug simple program >>>>>>>> pr

Re: [lldb-dev] lldb status at windows

2016-01-23 Thread Red Skotina via lldb-dev
gt;>>>> What's the command line you used with clang? >>>>>>> >>>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina >>>>>>> wrote: >>>>>>> >>>>>>>> Look like I m

Re: [lldb-dev] lldb status at windows

2016-02-02 Thread Red Skotina via lldb-dev
p. >>>>>>>> >>>>>>>> That said, it's not supposed to hang, but it is supposed to not >>>>>>>> work. >>>>>>>> >>>>>>>> What's the command line you used with clang? >&g

[lldb-dev] Status of prettyprint via MI

2016-02-07 Thread Red Skotina via lldb-dev
How i can use prettyprint for STL structures via MI (lldb-mi)? Have it is difference from gdb ? It is implemented? I use lldb at windows and want use lldb-mi like gdb via MI inside IDE Codelite with pretty printing of stl structures. I can now do basic debug with lldb-mi, but when try examine var