[lldb-dev] lldb status at windows
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
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 about what > worked, what didn't work, what's missing, etc. Anything that doesn't work > is a bug that I would like to fix. > > On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner wrote: > >> Hi, I guess I should make a new blog post at some point, or post status >> 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 >> expressions, etc. >> * Step-over might be unstable 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 is >> support for windows minidump files. So you can create a minidump of a >> stopped process from inside LLDB, and you can load up a minidump and do >> post-mortem debugging. >> >> On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >>> 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 >>> >> ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] LLDB build at windows
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.metaproj" (целевой объект по умолчанию) ( 2) -> "d:\code\llvm\build\projects\lldb\finish_swig.vcxproj.metaproj" (целевой объект по умолчанию) (482) -> "d:\code\llvm\build\projects\lldb\source\API\liblldb.vcxproj.metaproj" (целевой объект по умолчанию) (483) -> "d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC\lldbPluginObjCLa nguage.vcxproj.metaproj" (целевой объект по умолчанию) (570) -> "d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC\lldbPluginObjCLa nguage.vcxproj" (целевой объект по умолчанию) (571) -> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal error C10 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or direct ory (compiling source file D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu age\ObjC\Cocoa.cpp) [d:\code\llvm\build\projects\lldb\source\Plugins\Language\O bjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal error C10 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or direct ory (compiling source file D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu age\ObjC\NSArray.cpp) [d:\code\llvm\build\projects\lldb\source\Plugins\Language \ObjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal error C10 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or direct ory (compiling source file D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu age\ObjC\ObjCLanguage.cpp) [d:\code\llvm\build\projects\lldb\source\Plugins\Lan guage\ObjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal error C10 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or direct ory (compiling source file D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu age\ObjC\CF.cpp) [d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC \lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/Basic/DiagnosticIDs.h(53): fatal error C1083: Cannot open include file: 'clang/Basic/DiagnosticCommonKinds.inc': No such file or directory (compiling source file D:\code\llvm\llvm\projects\ll db\source\Plugins\Language\ObjC\NSDictionary.cpp) [d:\code\llvm\build\projects\ lldb\source\Plugins\Language\ObjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/Basic/DiagnosticIDs.h(53): fatal error C1083: Cannot open include file: 'clang/Basic/DiagnosticCommonKinds.inc': No such file or directory (compiling source file D:\code\llvm\llvm\projects\ll db\source\Plugins\Language\ObjC\NSError.cpp) [d:\code\llvm\build\projects\lldb\ source\Plugins\Language\ObjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/Basic/DiagnosticIDs.h(53): fatal error C1083: Cannot open include file: 'clang/Basic/DiagnosticCommonKinds.inc': No such file or directory (compiling source file D:\code\llvm\llvm\projects\ll db\source\Plugins\Language\ObjC\NSException.cpp) [d:\code\llvm\build\projects\l ldb\source\Plugins\Language\ObjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal error C10 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or direct ory (compiling source file D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu age\ObjC\NSIndexPath.cpp) [d:\code\llvm\build\projects\lldb\source\Plugins\Lang uage\ObjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal error C10 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or direct ory (compiling source file D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu age\ObjC\NSSet.cpp) [d:\code\llvm\build\projects\lldb\source\Plugins\Language\O bjC\lldbPluginObjCLanguage.vcxproj] D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal error C10 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or direct ory (compiling source file D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu age\ObjC\NSString.cpp) [d:\code\llvm\build\projects\lldb\source\Plugins\Languag e\ObjC\lldbPluginObjCLanguage.vcxproj] ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB build at windows
thanks. i still have 5 errors while linking "d:\code\llvm\build\LLVM.sln" (целевой объект по умолчанию) (1) -> "d:\code\llvm\build\tools\lldb\unittests\LLDBUnitTests.vcxproj.metaproj" (целев ой объект по умолчанию) (741) -> "d:\code\llvm\build\tools\lldb\unittests\Utility\UtilityTests.vcxproj.metaproj" (целевой объект по умолчанию) (742) -> "d:\code\llvm\build\tools\lldb\unittests\Utility\UtilityTests.vcxproj" (целевой объект по умолчанию) (743) -> 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 Studio 14 2015" -DCMAKE_BUILD_TYPE=Release -DLLVM_INCLUDE_EXAMPLES=OFF -DLLVM_INCLUDE_TESTS=OFF -DCLANG_INCLUDE_EXAMPLES=OFF -DCLANG_INCLUDE_TESTS=OFF -DPYTHON_HOME= ..\llvm msbuild LLVM.sln /p:Configuration=Release;Platform=Win32 i look to llvm\tools\lldb\gtest and cant find any file. here is 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 > |__ 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, 2016 at 1:29 PM Red Skotina via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> 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.metaproj" (целевой объект по >> умолчанию) ( >> 2) -> >> "d:\code\llvm\build\projects\lldb\finish_swig.vcxproj.metaproj" (целевой >> объект >> по умолчанию) (482) -> >> "d:\code\llvm\build\projects\lldb\source\API\liblldb.vcxproj.metaproj" >> (целевой >> объект по умолчанию) (483) -> >> >> "d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC\lldbPluginObjCLa >> nguage.vcxproj.metaproj" (целевой объект по умолчанию) (570) -> >> >> "d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC\lldbPluginObjCLa >> nguage.vcxproj" (целевой объект по умолчанию) (571) -> >> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal >> error C10 >> 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or >> direct >> ory (compiling source file >> D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu >> age\ObjC\Cocoa.cpp) >> [d:\code\llvm\build\projects\lldb\source\Plugins\Language\O >> bjC\lldbPluginObjCLanguage.vcxproj] >> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal >> error C10 >> 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or >> direct >> ory (compiling source file >> D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu >> age\ObjC\NSArray.cpp) >> [d:\code\llvm\build\projects\lldb\source\Plugins\Language >> \ObjC\lldbPluginObjCLanguage.vcxproj] >> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal >> error C10 >> 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or >> direct >> ory (compiling source file >> D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu >> age\ObjC\ObjCLanguage.cpp) >> [d:\code\llvm\build\projects\lldb\source\Plugins\Lan >> guage\ObjC\lldbPluginObjCLanguage.vcxproj] >> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal >> error C10 >> 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file or >> direct >> ory (compiling source file >> D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu >> age\ObjC\CF.cpp) >> [d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC >> \lldbPluginObjCLanguage.vcxproj] >> D:\code\llvm\llvm\tools\clang\include\clang/Basic/DiagnosticIDs.h(53): >> fatal >> error C1083: Cannot open include file: >> 'clang/Basic/DiagnosticCommonKinds.inc': >> No such file or directory (compiling source file >> D:\code\llvm\llvm\projects\ll >> db\source\Plugins\Language\ObjC\NSDictionary.cpp) >> [d:\code\llvm\build\projects\ >> lldb\source\Plugins\Language\ObjC\lldbPluginObjCLanguage.vcxproj] >> D:\code\llvm\llvm\tools\
Re: [lldb-dev] LLDB build at windows
thanks. i build successefuly llvm and lldb with ninja and cl compiler. If i build VS solution without options on CMake then i have ever more errors around unittests in llvm. like that: "d:\code\llvm\build\LLVM.sln" (целевой объект по умолчанию) (1) -> "d:\code\llvm\build\unittests\ADT\ADTTests.vcxproj.metaproj" (целевой объект по умолчанию) (749) -> "d:\code\llvm\build\unittests\ADT\ADTTests.vcxproj" (целевой объект по умолчани ю) (750) -> (Целевой объект ClCompile) -> D:\code\llvm\llvm\include\llvm/ADT/PointerEmbeddedInt.h(33): error C2327: 'll vm::PointerEmbeddedInt::Value': is not a type name, static, or enume rator (compiling source file D:\code\llvm\llvm\unittests\ADT\PointerEmbeddedInt Test.cpp) [d:\code\llvm\build\unittests\ADT\ADTTests.vcxproj] D:\code\llvm\llvm\include\llvm/ADT/PointerEmbeddedInt.h(33): error C2065: 'Va lue': undeclared identifier (compiling source file D:\code\llvm\llvm\unittests\ ADT\PointerEmbeddedIntTest.cpp) [d:\code\llvm\build\unittests\ADT\ADTTests.vcxp roj] D:\code\llvm\llvm\include\llvm/ADT/PointerEmbeddedInt.h(33): error C2327: 'll vm::PointerEmbeddedInt::Value': is not a type name, static, or enumerato r (compiling source file D:\code\llvm\llvm\unittests\ADT\PointerEmbeddedIntTest .cpp) [d:\code\llvm\build\unittests\ADT\ADTTests.vcxproj] D:\code\llvm\llvm\include\llvm/ADT/PointerEmbeddedInt.h(34): error C2338: Can not embed more bits than we have in a pointer! (compiling source file D:\code\l lvm\llvm\unittests\ADT\PointerEmbeddedIntTest.cpp) [d:\code\llvm\build\unittest s\ADT\ADTTests.vcxproj] D:\code\llvm\llvm\include\llvm/ADT/PointerEmbeddedInt.h(39): error C2327: 'll vm::PointerEmbeddedInt::Value': is not a type name, static, or enumerato r (compiling source file D:\code\llvm\llvm\unittests\ADT\PointerEmbeddedIntTest .cpp) [d:\code\llvm\build\unittests\ADT\ADTTests.vcxproj] D:\code\llvm\llvm\include\llvm/ADT/PointerEmbeddedInt.h(39): error C2065: 'Va lue': undeclared identifier (compiling source file D:\code\llvm\llvm\unittests\ ADT\PointerEmbeddedIntTest.cpp) [d:\code\llvm\build\unittests\ADT\ADTTests.vcxp roj] 2016-01-11 0:56 GMT+03:00 Zachary Turner : > I have never built with -DLLVM_INCLUDE_TESTS=OFF > -DCLANG_INCLUDE_EXAMPLES=OFF -DCLANG_INCLUDE_TESTS=OFF before, so that > could be related. Can you try removing those options on CMake to see if > that fixes it? > > The other thing I do differently is I use ninja generator. So I use -G > Ninja instead of -G "Visual Studio 14 2015". Building from within Visual > Studio like you're doing is supposed to work, I just don't know if anyone > tests it. My command line is usually: > > cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DPYTHON_HOME= python\x86 from dest variable> ..\llvm > > ninja > > > On Sun, Jan 10, 2016 at 4:02 AM Red Skotina wrote: > >> thanks. >> i still have 5 errors while linking >> "d:\code\llvm\build\LLVM.sln" (целевой объект по умолчанию) (1) -> >> "d:\code\llvm\build\tools\lldb\unittests\LLDBUnitTests.vcxproj.metaproj" >> (целев >> ой объект по умолчанию) (741) -> >> >> "d:\code\llvm\build\tools\lldb\unittests\Utility\UtilityTests.vcxproj.metaproj" >> (целевой объект по умолчанию) (742) -> >> "d:\code\llvm\build\tools\lldb\unittests\Utility\UtilityTests.vcxproj" >> (целевой >> объект по умолчанию) (743) -> >> 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 Studio 14 2015" -DCMAKE_BUILD_TYPE=Release >> -DLLVM_INCLUDE_EXAMPLES=OFF -DLLVM_INCLUDE_TESTS=OFF >> -DCLANG_INCLUDE_EXAMPLES=OFF -DCLANG_INCLUDE_TESTS=OFF >> -DPYTHON_HOME= ..\llvm >> >> msbuild LLVM.sln /p:Configuration=Release;Platform=Win32 >> >> i look to llvm\tools\lldb\gtest and cant find any file. here is 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 >>> |__ 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, 2016 at 1:29 PM Red Skotina via lldb-dev < >>> lldb-dev@lists.llvm.org> wrote: >>> >>>> If i want
Re: [lldb-dev] LLDB build at windows
ой объект по умолчанию) (741) -> >>>> >>>> "d:\code\llvm\build\tools\lldb\unittests\Utility\UtilityTests.vcxproj.metaproj" >>>> (целевой объект по умолчанию) (742) -> >>>> "d:\code\llvm\build\tools\lldb\unittests\Utility\UtilityTests.vcxproj" >>>> (целевой >>>> объект по умолчанию) (743) -> >>>> 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 Studio 14 2015" -DCMAKE_BUILD_TYPE=Release >>>> -DLLVM_INCLUDE_EXAMPLES=OFF -DLLVM_INCLUDE_TESTS=OFF >>>> -DCLANG_INCLUDE_EXAMPLES=OFF -DCLANG_INCLUDE_TESTS=OFF >>>> -DPYTHON_HOME= ..\llvm >>>> >>>> msbuild LLVM.sln /p:Configuration=Release;Platform=Win32 >>>> >>>> i look to llvm\tools\lldb\gtest and cant find any file. here is 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 >>>>> |__ 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, 2016 at 1:29 PM Red Skotina via lldb-dev < >>>>> lldb-dev@lists.llvm.org> wrote: >>>>> >>>>>> 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.metaproj" (целевой объект по >>>>>> умолчанию) ( >>>>>> 2) -> >>>>>> "d:\code\llvm\build\projects\lldb\finish_swig.vcxproj.metaproj" >>>>>> (целевой объект >>>>>> по умолчанию) (482) -> >>>>>> "d:\code\llvm\build\projects\lldb\source\API\liblldb.vcxproj.metaproj" >>>>>> (целевой >>>>>> объект по умолчанию) (483) -> >>>>>> >>>>>> "d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC\lldbPluginObjCLa >>>>>> nguage.vcxproj.metaproj" (целевой объект по умолчанию) (570) -> >>>>>> >>>>>> "d:\code\llvm\build\projects\lldb\source\Plugins\Language\ObjC\lldbPluginObjCLa >>>>>> nguage.vcxproj" (целевой объект по умолчанию) (571) -> >>>>>> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal >>>>>> error C10 >>>>>> 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file >>>>>> or direct >>>>>> ory (compiling source file >>>>>> D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu >>>>>> age\ObjC\Cocoa.cpp) >>>>>> [d:\code\llvm\build\projects\lldb\source\Plugins\Language\O >>>>>> bjC\lldbPluginObjCLanguage.vcxproj] >>>>>> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal >>>>>> error C10 >>>>>> 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file >>>>>> or direct >>>>>> ory (compiling source file >>>>>> D:\code\llvm\llvm\projects\lldb\source\Plugins\Langu >>>>>> age\ObjC\NSArray.cpp) >>>>>> [d:\code\llvm\build\projects\lldb\source\Plugins\Language >>>>>> \ObjC\lldbPluginObjCLanguage.vcxproj] >>>>>> D:\code\llvm\llvm\tools\clang\include\clang/AST/ASTFwd.h(22): fatal >>>>>> error C10 >>>>>> 83: Cannot open include file: 'clang/AST/DeclNodes.inc': No such file >>>>>> or direct >>>>>> ory (compiling so
Re: [lldb-dev] lldb status at windows
Look like I miss something , but i cant debug simple program program
compiled with clang from trunk (258016), msvc 2015 stdlib, from vs2015 x86
developer console .
i use lldb from trunk
#include "stdio.h"
int main(int argc, char **argv)
{
printf("hello1\n");
printf("hello2\n");
return 0;
}
d:\code\tests\test2>lldb a.exe
(lldb) target create "a.exe"
Current executable set to 'a.exe' (i686).
(lldb) run
Process 6264 launching
---
a.exe and lldb hangs
What i doing wrong ?
2016-01-08 0:42 GMT+03:00 Red Skotina :
> 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 about
>> what worked, what didn't work, what's missing, etc. Anything that doesn't
>> work is a bug that I would like to fix.
>>
>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner
>> wrote:
>>
>>> Hi, I guess I should make a new blog post at some point, or post status
>>> 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
>>> expressions, etc.
>>> * Step-over might be unstable 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 is
>>> support for windows minidump files. So you can create a minidump of a
>>> stopped process from inside LLDB, and you can load up a minidump and do
>>> post-mortem debugging.
>>>
>>> On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev <
>>> lldb-dev@lists.llvm.org> wrote:
>>>
>>>> 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
>>>>
>>>
>
___
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
yes, i miss it. but anyway dont work
d:\code\Unity_Unpacker\tests\test2>clang -v -fuse-ld=lld main.cpp
clang version 3.9.0 (trunk 258509)
Target: i686-pc-windows-msvc
Thread model: posix
InstalledDir: d:\code\llvm\build\bin
"d:\\code\\llvm\\build\\bin\\clang.exe" -cc1 -triple
i686-pc-windows-msvc18.0.0
-emit-obj -mrelax-all -mincremental-linker-compatible -disable-free
-disable-ll
vm-verifier -main-file-name main.cpp -mrelocation-model static
-mthread-model po
six -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-target-c
pu pentium4 -v -dwarf-column-info -debugger-tuning=gdb -resource-dir
"d:\\code\\
llvm\\build\\bin\\..\\lib\\clang\\3.9.0" -internal-isystem
"d:\\code\\llvm\\buil
d\\bin\\..\\lib\\clang\\3.9.0\\include" -internal-isystem "C:\\Program
Files (x8
6)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE" -internal-isystem
"C:\\Program Fi
les (x86)\\Microsoft Visual Studio 14.0\\VC\\ATLMFC\\INCLUDE"
-internal-isystem
"C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.10240.0\\ucrt"
-intern
al-isystem "C:\\Program Files (x86)\\Windows
Kits\\NETFXSDK\\4.6.1\\include\\um"
-internal-isystem "C:\\Program Files (x86)\\Windows
Kits\\8.1\\includeshare
d" -internal-isystem "C:\\Program Files (x86)\\Windows
Kits\\8.1\\includeum"
-internal-isystem "C:\\Program Files (x86)\\Windows
Kits\\8.1\\includewinrt
" -fdeprecated-macro -fdebug-compilation-dir
"d:\\code\\Unity_Unpacker\\tests\\t
est2" -ferror-limit 19 -fmessage-length 80 -fms-extensions
-fms-compatibility -f
ms-compatibility-version=18 -std=c++11 -fno-threadsafe-statics
-fdelayed-templat
e-parsing -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics
-o "C
:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o" -x c++ main.cpp
clang -cc1 version 3.9.0 based upon LLVM 3.9.0svn default target
i686-pc-windows
-msvc
#include "..." search starts here:
#include <...> search starts here:
d:\code\llvm\build\bin\..\lib\clang\3.9.0\include
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE
C:\Program Files (x86)\Windows Kits\10\include\10.0.10240.0\ucrt
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um
C:\Program Files (x86)\Windows Kits\8.1\include\\shared
C:\Program Files (x86)\Windows Kits\8.1\include\\um
C:\Program Files (x86)\Windows Kits\8.1\include\\winrt
End of search list.
"d:\\code\\llvm\\build\\bin\\lld-link.exe" -out:a.exe -defaultlib:libcmt
-nolog
o "C:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o"
d:\code\Unity_Unpacker\tests\test2>lldb a.exe
(lldb) target create "a.exe"
Current executable set to 'a.exe' (i686).
(lldb) run
Process 6448 launching
--
process hang
2016-01-22 22:13 GMT+03:00 Zachary Turner :
> When you compile, you need to use -fuse-ld=lld. Most people miss this
> step.
>
> That said, it's not supposed to hang, but it is supposed to not work.
>
> What's the command line you used with clang?
>
> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina
> wrote:
>
>> Look like I miss something , but i cant debug simple program program
>> compiled with clang from trunk (258016), msvc 2015 stdlib, from vs2015 x86
>> developer console .
>> i use lldb from trunk
>> #include "stdio.h"
>>
>> int main(int argc, char **argv)
>> {
>> printf("hello1\n");
>> printf("hello2\n");
>> return 0;
>> }
>>
>> d:\code\tests\test2>lldb a.exe
>> (lldb) target create "a.exe"
>> Current executable set to 'a.exe' (i686).
>> (lldb) run
>>
>> Process 6264 launching
>>
>> ---
>> a.exe and lldb hangs
>>
>> What i doing wrong ?
>>
>>
>> 2016-01-08 0:42 GMT+03:00 Red Skotina :
>>
>>> 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 about
>>>> what worked, what didn't work, what's missing, etc. Anything that doesn't
>>>> work is a bug that I would like to fix.
>>>>
>>>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner
>>>> wrote:
>>>>
>>>>> Hi, I guess I should make a new blog post at some point, or post
>>>>> status on the website. Here's my best estimate at what you can expect.
>>>>>
>>>>> * Most common debugging scenarios should work. Run under debugger,
>&
Re: [lldb-dev] lldb status at windows
t;>> {
>>>> printf("hello1\n");
>>>> printf("hello2\n");
>>>> return 0;
>>>> }
>>>>
>>>> d:\code\tests\test2>lldb a.exe
>>>> (lldb) target create "a.exe"
>>>> Current executable set to 'a.exe' (i686).
>>>> (lldb) run
>>>>
>>>> Process 6264 launching
>>>>
>>>> ---
>>>> a.exe and lldb hangs
>>>>
>>>> What i doing wrong ?
>>>>
>>>>
>>>> 2016-01-08 0:42 GMT+03:00 Red Skotina :
>>>>
>>>>> 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 about
>>>>>> what worked, what didn't work, what's missing, etc. Anything that
>>>>>> doesn't
>>>>>> work is a bug that I would like to fix.
>>>>>>
>>>>>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner
>>>>>> wrote:
>>>>>>
>>>>>>> Hi, I guess I should make a new blog post at some point, or post
>>>>>>> status 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
>>>>>>> expressions, etc.
>>>>>>> * Step-over might be unstable 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 is support for windows minidump files. So you can create a
>>>>>>> minidump
>>>>>>> of a stopped process from inside LLDB, and you can load up a minidump
>>>>>>> and
>>>>>>> do post-mortem debugging.
>>>>>>>
>>>>>>> On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev <
>>>>>>> lldb-dev@lists.llvm.org> wrote:
>>>>>>>
>>>>>>>> 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
>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>
___
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
>>>> "d:\\code\\llvm\\build\\bin\\lld-link.exe" -out:a.exe
>>>> -defaultlib:libcmt -nolog
>>>> o "C:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o"
>>>>
>>>> d:\code\Unity_Unpacker\tests\test2>lldb a.exe
>>>> (lldb) target create "a.exe"
>>>> Current executable set to 'a.exe' (i686).
>>>> (lldb) run
>>>>
>>>> Process 6448 launching
>>>>
>>>> --
>>>> process hang
>>>>
>>>> 2016-01-22 22:13 GMT+03:00 Zachary Turner :
>>>>
>>>>> When you compile, you need to use -fuse-ld=lld. Most people miss this
>>>>> step.
>>>>>
>>>>> That said, it's not supposed to hang, but it is supposed to not work.
>>>>>
>>>>> What's the command line you used with clang?
>>>>>
>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina
>>>>> wrote:
>>>>>
>>>>>> Look like I miss something , but i cant debug simple program program
>>>>>> compiled with clang from trunk (258016), msvc 2015 stdlib, from vs2015
>>>>>> x86
>>>>>> developer console .
>>>>>> i use lldb from trunk
>>>>>> #include "stdio.h"
>>>>>>
>>>>>> int main(int argc, char **argv)
>>>>>> {
>>>>>> printf("hello1\n");
>>>>>> printf("hello2\n");
>>>>>> return 0;
>>>>>> }
>>>>>>
>>>>>> d:\code\tests\test2>lldb a.exe
>>>>>> (lldb) target create "a.exe"
>>>>>> Current executable set to 'a.exe' (i686).
>>>>>> (lldb) run
>>>>>>
>>>>>> Process 6264 launching
>>>>>>
>>>>>> ---
>>>>>> a.exe and lldb hangs
>>>>>>
>>>>>> What i doing wrong ?
>>>>>>
>>>>>>
>>>>>> 2016-01-08 0:42 GMT+03:00 Red Skotina :
>>>>>>
>>>>>>> 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
>>>>>>>> about what worked, what didn't work, what's missing, etc. Anything
>>>>>>>> that
>>>>>>>> doesn't work is a bug that I would like to fix.
>>>>>>>>
>>>>>>>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi, I guess I should make a new blog post at some point, or post
>>>>>>>>> status 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 expressions, etc.
>>>>>>>>> * Step-over might be unstable 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 is support for windows minidump files. So you can create a
>>>>>>>>> minidump
>>>>>>>>> of a stopped process from inside LLDB, and you can load up a minidump
>>>>>>>>> and
>>>>>>>>> do post-mortem debugging.
>>>>>>>>>
>>>>>>>>> On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev <
>>>>>>>>> lldb-dev@lists.llvm.org> wrote:
>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>
___
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
;> -fdelayed-templat
>>>>>> e-parsing -fobjc-runtime=gcc -fdiagnostics-show-option
>>>>>> -fcolor-diagnostics -o "C
>>>>>> :\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o" -x c++ main.cpp
>>>>>> clang -cc1 version 3.9.0 based upon LLVM 3.9.0svn default target
>>>>>> i686-pc-windows
>>>>>> -msvc
>>>>>> #include "..." search starts here:
>>>>>> #include <...> search starts here:
>>>>>> d:\code\llvm\build\bin\..\lib\clang\3.9.0\include
>>>>>> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE
>>>>>> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE
>>>>>> C:\Program Files (x86)\Windows Kits\10\include\10.0.10240.0\ucrt
>>>>>> C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um
>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\shared
>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\um
>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\winrt
>>>>>> End of search list.
>>>>>> "d:\\code\\llvm\\build\\bin\\lld-link.exe" -out:a.exe
>>>>>> -defaultlib:libcmt -nolog
>>>>>> o "C:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o"
>>>>>>
>>>>>> d:\code\Unity_Unpacker\tests\test2>lldb a.exe
>>>>>> (lldb) target create "a.exe"
>>>>>> Current executable set to 'a.exe' (i686).
>>>>>> (lldb) run
>>>>>>
>>>>>> Process 6448 launching
>>>>>>
>>>>>> --
>>>>>> process hang
>>>>>>
>>>>>> 2016-01-22 22:13 GMT+03:00 Zachary Turner :
>>>>>>
>>>>>>> When you compile, you need to use -fuse-ld=lld. Most people miss
>>>>>>> this step.
>>>>>>>
>>>>>>> That said, it's not supposed to hang, but it is supposed to not work.
>>>>>>>
>>>>>>> What's the command line you used with clang?
>>>>>>>
>>>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Look like I miss something , but i cant debug simple program
>>>>>>>> program compiled with clang from trunk (258016), msvc 2015 stdlib, from
>>>>>>>> vs2015 x86 developer console .
>>>>>>>> i use lldb from trunk
>>>>>>>> #include "stdio.h"
>>>>>>>>
>>>>>>>> int main(int argc, char **argv)
>>>>>>>> {
>>>>>>>> printf("hello1\n");
>>>>>>>> printf("hello2\n");
>>>>>>>> return 0;
>>>>>>>> }
>>>>>>>>
>>>>>>>> d:\code\tests\test2>lldb a.exe
>>>>>>>> (lldb) target create "a.exe"
>>>>>>>> Current executable set to 'a.exe' (i686).
>>>>>>>> (lldb) run
>>>>>>>>
>>>>>>>> Process 6264 launching
>>>>>>>>
>>>>>>>> ---
>>>>>>>> a.exe and lldb hangs
>>>>>>>>
>>>>>>>> What i doing wrong ?
>>>>>>>>
>>>>>>>>
>>>>>>>> 2016-01-08 0:42 GMT+03:00 Red Skotina :
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>> about what worked, what didn't work, what's missing, etc. Anything
>>>>>>>>>> that
>>>>>>>>>> doesn't work is a bug that I would like to fix.
>>>>>>>>>>
>>>>>>>>>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner <
>>>>>>>>>> ztur...@google.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi, I guess I should make a new blog post at some point, or post
>>>>>>>>>>> status 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 expressions, etc.
>>>>>>>>>>> * Step-over might be unstable 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 is support for windows minidump files. So you can create a
>>>>>>>>>>> minidump
>>>>>>>>>>> of a stopped process from inside LLDB, and you can load up a
>>>>>>>>>>> minidump and
>>>>>>>>>>> do post-mortem debugging.
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev <
>>>>>>>>>>> lldb-dev@lists.llvm.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>
___
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
;>>>>> " -fdeprecated-macro -fdebug-compilation-dir
>>>>>> "d:\\code\\Unity_Unpacker\\tests\\t
>>>>>> est2" -ferror-limit 19 -fmessage-length 80 -fms-extensions
>>>>>> -fms-compatibility -f
>>>>>> ms-compatibility-version=18 -std=c++11 -fno-threadsafe-statics
>>>>>> -fdelayed-templat
>>>>>> e-parsing -fobjc-runtime=gcc -fdiagnostics-show-option
>>>>>> -fcolor-diagnostics -o "C
>>>>>> :\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o" -x c++ main.cpp
>>>>>> clang -cc1 version 3.9.0 based upon LLVM 3.9.0svn default target
>>>>>> i686-pc-windows
>>>>>> -msvc
>>>>>> #include "..." search starts here:
>>>>>> #include <...> search starts here:
>>>>>> d:\code\llvm\build\bin\..\lib\clang\3.9.0\include
>>>>>> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE
>>>>>> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE
>>>>>> C:\Program Files (x86)\Windows Kits\10\include\10.0.10240.0\ucrt
>>>>>> C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um
>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\shared
>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\um
>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\winrt
>>>>>> End of search list.
>>>>>> "d:\\code\\llvm\\build\\bin\\lld-link.exe" -out:a.exe
>>>>>> -defaultlib:libcmt -nolog
>>>>>> o "C:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o"
>>>>>>
>>>>>> d:\code\Unity_Unpacker\tests\test2>lldb a.exe
>>>>>> (lldb) target create "a.exe"
>>>>>> Current executable set to 'a.exe' (i686).
>>>>>> (lldb) run
>>>>>>
>>>>>> Process 6448 launching
>>>>>>
>>>>>> --
>>>>>> process hang
>>>>>>
>>>>>> 2016-01-22 22:13 GMT+03:00 Zachary Turner :
>>>>>>
>>>>>>> When you compile, you need to use -fuse-ld=lld. Most people miss
>>>>>>> this step.
>>>>>>>
>>>>>>> That said, it's not supposed to hang, but it is supposed to not work.
>>>>>>>
>>>>>>> What's the command line you used with clang?
>>>>>>>
>>>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Look like I miss something , but i cant debug simple program
>>>>>>>> program compiled with clang from trunk (258016), msvc 2015 stdlib, from
>>>>>>>> vs2015 x86 developer console .
>>>>>>>> i use lldb from trunk
>>>>>>>> #include "stdio.h"
>>>>>>>>
>>>>>>>> int main(int argc, char **argv)
>>>>>>>> {
>>>>>>>> printf("hello1\n");
>>>>>>>> printf("hello2\n");
>>>>>>>> return 0;
>>>>>>>> }
>>>>>>>>
>>>>>>>> d:\code\tests\test2>lldb a.exe
>>>>>>>> (lldb) target create "a.exe"
>>>>>>>> Current executable set to 'a.exe' (i686).
>>>>>>>> (lldb) run
>>>>>>>>
>>>>>>>> Process 6264 launching
>>>>>>>>
>>>>>>>> ---
>>>>>>>> a.exe and lldb hangs
>>>>>>>>
>>>>>>>> What i doing wrong ?
>>>>>>>>
>>>>>>>>
>>>>>>>> 2016-01-08 0:42 GMT+03:00 Red Skotina :
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>> about what worked, what didn't work, what's missing, etc. Anything
>>>>>>>>>> that
>>>>>>>>>> doesn't work is a bug that I would like to fix.
>>>>>>>>>>
>>>>>>>>>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner <
>>>>>>>>>> ztur...@google.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi, I guess I should make a new blog post at some point, or post
>>>>>>>>>>> status 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 expressions, etc.
>>>>>>>>>>> * Step-over might be unstable 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 is support for windows minidump files. So you can create a
>>>>>>>>>>> minidump
>>>>>>>>>>> of a stopped process from inside LLDB, and you can load up a
>>>>>>>>>>> minidump and
>>>>>>>>>>> do post-mortem debugging.
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev <
>>>>>>>>>>> lldb-dev@lists.llvm.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>
___
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
t;>>>>>> al-isystem "C:\\Program Files (x86)\\Windows
>>>>>>> Kits\\NETFXSDK\\4.6.1\\include\\um"
>>>>>>> -internal-isystem "C:\\Program Files (x86)\\Windows
>>>>>>> Kits\\8.1\\includeshare
>>>>>>> d" -internal-isystem "C:\\Program Files (x86)\\Windows
>>>>>>> Kits\\8.1\\includeum"
>>>>>>> -internal-isystem "C:\\Program Files (x86)\\Windows
>>>>>>> Kits\\8.1\\includewinrt
>>>>>>> " -fdeprecated-macro -fdebug-compilation-dir
>>>>>>> "d:\\code\\Unity_Unpacker\\tests\\t
>>>>>>> est2" -ferror-limit 19 -fmessage-length 80 -fms-extensions
>>>>>>> -fms-compatibility -f
>>>>>>> ms-compatibility-version=18 -std=c++11 -fno-threadsafe-statics
>>>>>>> -fdelayed-templat
>>>>>>> e-parsing -fobjc-runtime=gcc -fdiagnostics-show-option
>>>>>>> -fcolor-diagnostics -o "C
>>>>>>> :\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o" -x c++ main.cpp
>>>>>>> clang -cc1 version 3.9.0 based upon LLVM 3.9.0svn default target
>>>>>>> i686-pc-windows
>>>>>>> -msvc
>>>>>>> #include "..." search starts here:
>>>>>>> #include <...> search starts here:
>>>>>>> d:\code\llvm\build\bin\..\lib\clang\3.9.0\include
>>>>>>> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE
>>>>>>> C:\Program Files (x86)\Microsoft Visual Studio
>>>>>>> 14.0\VC\ATLMFC\INCLUDE
>>>>>>> C:\Program Files (x86)\Windows Kits\10\include\10.0.10240.0\ucrt
>>>>>>> C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um
>>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\shared
>>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\um
>>>>>>> C:\Program Files (x86)\Windows Kits\8.1\include\\winrt
>>>>>>> End of search list.
>>>>>>> "d:\\code\\llvm\\build\\bin\\lld-link.exe" -out:a.exe
>>>>>>> -defaultlib:libcmt -nolog
>>>>>>> o "C:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o"
>>>>>>>
>>>>>>> d:\code\Unity_Unpacker\tests\test2>lldb a.exe
>>>>>>> (lldb) target create "a.exe"
>>>>>>> Current executable set to 'a.exe' (i686).
>>>>>>> (lldb) run
>>>>>>>
>>>>>>> Process 6448 launching
>>>>>>>
>>>>>>> --
>>>>>>> process hang
>>>>>>>
>>>>>>> 2016-01-22 22:13 GMT+03:00 Zachary Turner :
>>>>>>>
>>>>>>>> When you compile, you need to use -fuse-ld=lld. Most people miss
>>>>>>>> this step.
>>>>>>>>
>>>>>>>> That said, it's not supposed to hang, but it is supposed to not
>>>>>>>> work.
>>>>>>>>
>>>>>>>> What's the command line you used with clang?
>>>>>>>>
>>>>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Look like I miss something , but i cant debug simple program
>>>>>>>>> program compiled with clang from trunk (258016), msvc 2015 stdlib,
>>>>>>>>> from
>>>>>>>>> vs2015 x86 developer console .
>>>>>>>>> i use lldb from trunk
>>>>>>>>> #include "stdio.h"
>>>>>>>>>
>>>>>>>>> int main(int argc, char **argv)
>>>>>>>>> {
>>>>>>>>> printf("hello1\n");
>>>>>>>>> printf("hello2\n");
>>>>>>>>> return 0;
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> d:\code\tests\test2>lldb a.exe
>>>>>>>>> (lldb) target create "a.exe"
>>>>>>>>> Current executable set to 'a.exe' (i686).
>>>>>>>>> (lldb) run
>>>>>>>>>
>>>>>>>>> Process 6264 launching
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> a.exe and lldb hangs
>>>>>>>>>
>>>>>>>>> What i doing wrong ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2016-01-08 0:42 GMT+03:00 Red Skotina :
>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>>> about what worked, what didn't work, what's missing, etc. Anything
>>>>>>>>>>> that
>>>>>>>>>>> doesn't work is a bug that I would like to fix.
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner <
>>>>>>>>>>> ztur...@google.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi, I guess I should make a new blog post at some point, or
>>>>>>>>>>>> post status 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 expressions, etc.
>>>>>>>>>>>> * Step-over might be unstable 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 is support for windows minidump files. So you can
>>>>>>>>>>>> create a
>>>>>>>>>>>> minidump of a stopped process from inside LLDB, and you can load
>>>>>>>>>>>> up a
>>>>>>>>>>>> minidump and do post-mortem debugging.
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev <
>>>>>>>>>>>> lldb-dev@lists.llvm.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> 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
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>>>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] Status of prettyprint via MI
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 variables take some errors. DEBUG>>0199-var-create - @ "vector_of_obj" DEBUG>>0199^error,msg="Command 'var-create'. Option 'frame' not found" It is just not implemented or dynamic variables cant used ? ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
