<div dir="ltr">I'm out of office until Monday, but I'll try to reproduce this then and update. Never seen a hang before, so I wonder if there's something different about your machine that we haven't thought of or taken into account. Either way I'll update Monday.</div><br><div class="gmail_quote"><div dir="ltr">On Sat, Jan 23, 2016 at 12:57 AM Red Skotina <<a href="mailto:red.skotina@gmail.com">red.skotina@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">same.<div><br></div><div><div>d:\code\Unity_Unpacker\tests\test2>clang -g -fuse-ld=lld main.cpp</div></div></div><div dir="ltr"><div><div><br></div><div>d:\code\Unity_Unpacker\tests\test2>lldb a.exe</div><div>(lldb) target create "a.exe"</div><div>Current executable set to 'a.exe' (i686).</div><div>(lldb) run</div><div><br></div></div></div><div dir="ltr"><div><div>Process 6984 launching</div></div><div>-------</div><div>hangs</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-23 11:54 GMT+03:00 Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ahh you probably need to add -g to clang, otherwise it's not generating debug info. I've never tried debugging a binary with no debug info. Obviously it shouldn't hang, but either way it's just not something we've tested on Windows.<div><br></div><div><br></div></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Sat, Jan 23, 2016 at 12:51 AM Red Skotina <<a href="mailto:red.skotina@gmail.com" target="_blank">red.skotina@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="font-size:12.8px">yes. i doing it. you can see what clang use </span><span style="font-size:12.8px;color:rgb(80,0,80)">d:\\code\\llvm\\build\\bin\\</span><span style="font-size:12.8px;color:rgb(80,0,80)">lld-link.exe</span><div style="font-size:12.8px"><span style="color:rgb(80,0,80);font-size:12.8px">but anyway it is hang :(</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-22 23:30 GMT+03:00 Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Under llvm/tools also checkout lld. So your directories should look like this:<div><br></div><div>llvm</div><div>\-- tools</div><div> \-- clang</div><div> \-- lldb</div><div> \-- lld</div><div><br></div><div>Then re-run cmake to generate build files again, recompile, and then it should work. Right now the problem is that lld-link.exe hasn't been compiled yet.</div></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 22, 2016 at 12:22 PM Red Skotina <<a href="mailto:red.skotina@gmail.com" target="_blank">red.skotina@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">yes, i miss it. but anyway dont work<div><br></div><div><br><div><div>d:\code\Unity_Unpacker\tests\test2>clang -v -fuse-ld=lld main.cpp</div><div>clang version 3.9.0 (trunk 258509)</div><div>Target: i686-pc-windows-msvc</div><div>Thread model: posix</div><div>InstalledDir: d:\code\llvm\build\bin</div><div> "d:\\code\\llvm\\build\\bin\\clang.exe" -cc1 -triple i686-pc-windows-msvc18.0.0</div><div> -emit-obj -mrelax-all -mincremental-linker-compatible -disable-free -disable-ll</div><div>vm-verifier -main-file-name main.cpp -mrelocation-model static -mthread-model po</div><div>six -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -target-c</div><div>pu pentium4 -v -dwarf-column-info -debugger-tuning=gdb -resource-dir "d:\\code\\</div><div>llvm\\build\\bin\\..\\lib\\clang\\3.9.0" -internal-isystem "d:\\code\\llvm\\buil</div><div>d\\bin\\..\\lib\\clang\\3.9.0\\include" -internal-isystem "C:\\Program Files (x8</div><div>6)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE" -internal-isystem "C:\\Program Fi</div><div>les (x86)\\Microsoft Visual Studio 14.0\\VC\\ATLMFC\\INCLUDE" -internal-isystem</div><div>"C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.10240.0\\ucrt" -intern</div><div>al-isystem "C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.6.1\\include\\um"</div><div> -internal-isystem "C:\\Program Files (x86)\\Windows Kits\\8.1\\include\\\\share</div><div>d" -internal-isystem "C:\\Program Files (x86)\\Windows Kits\\8.1\\include\\\\um"</div><div> -internal-isystem "C:\\Program Files (x86)\\Windows Kits\\8.1\\include\\\\winrt</div><div>" -fdeprecated-macro -fdebug-compilation-dir "d:\\code\\Unity_Unpacker\\tests\\t</div><div>est2" -ferror-limit 19 -fmessage-length 80 -fms-extensions -fms-compatibility -f</div><div>ms-compatibility-version=18 -std=c++11 -fno-threadsafe-statics -fdelayed-templat</div><div>e-parsing -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -o "C</div><div>:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o" -x c++ main.cpp</div><div>clang -cc1 version 3.9.0 based upon LLVM 3.9.0svn default target i686-pc-windows</div><div>-msvc</div><div>#include "..." search starts here:</div><div>#include <...> search starts here:</div><div> d:\code\llvm\build\bin\..\lib\clang\3.9.0\include</div><div> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE</div><div> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE</div><div> C:\Program Files (x86)\Windows Kits\10\include\10.0.10240.0\ucrt</div><div> C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um</div><div> C:\Program Files (x86)\Windows Kits\8.1\include\\shared</div><div> C:\Program Files (x86)\Windows Kits\8.1\include\\um</div><div> C:\Program Files (x86)\Windows Kits\8.1\include\\winrt</div><div>End of search list.</div><div> "d:\\code\\llvm\\build\\bin\\lld-link.exe" -out:a.exe -defaultlib:libcmt -nolog</div><div>o "C:\\Users\\Red\\AppData\\Local\\Temp\\main-71fc84.o"</div><div><br></div><div>d:\code\Unity_Unpacker\tests\test2>lldb a.exe</div></div></div></div><div dir="ltr"><div><div><div>(lldb) target create "a.exe"</div><div>Current executable set to 'a.exe' (i686).</div><div>(lldb) run</div><div><br></div></div></div></div><div dir="ltr"><div><div><div>Process 6448 launching</div></div><div><br></div></div><div>----------------------------------</div><div>process hang</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-22 22:13 GMT+03:00 Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">When you compile, you need to use -fuse-ld=lld. Most people miss this step.<div><br></div><div>That said, it's not supposed to hang, but it is supposed to not work.</div><div><br></div><div>What's the command line you used with clang?</div></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 22, 2016 at 11:08 AM Red Skotina <<a href="mailto:red.skotina@gmail.com" target="_blank">red.skotina@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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 .<div> i use lldb from trunk <div> #include "stdio.h"</div><div><br></div><div> int main(int argc, char **argv)</div><div> {</div><div> printf("hello1\n");</div><div> printf("hello2\n");</div><div> return 0;</div><div> }</div><div> </div><div><div>d:\code\tests\test2>lldb a.exe</div><div>(lldb) target create "a.exe"</div><div>Current executable set to 'a.exe' (i686).</div><div>(lldb) run</div><div><br></div><div>Process 6264 launching</div></div><div><br></div><div>---------------------------</div><div>a.exe and lldb hangs</div><div><br></div><div>What i doing wrong ?</div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-08 0:42 GMT+03:00 Red Skotina <span dir="ltr"><<a href="mailto:red.skotina@gmail.com" target="_blank">red.skotina@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Nice to hear. I should answer after some time of using</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-07 21:04 GMT+03:00 Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.</div><div><div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner <<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.<div><br></div><div>* Most common debugging scenarios should work. Run under debugger, attach to process, interrupt, continue, print variable values, evaluate expressions, etc.</div><div>* Step-over might be unstable in certain scenarios</div><div>* Conditional breakpoints don't work</div><div>* Hardware watchpoints don't work</div><div>* Expression evaluation might not work in some advanced cases.</div><div><br></div><div>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.</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 6, 2016 at 10:39 PM Red Skotina via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Where can i look lldb status for native debug at Windows?</div>
_______________________________________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
</blockquote></div></blockquote></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</blockquote></div>
</div></div></blockquote></div><br></div>
</blockquote></div>
</div></div></blockquote></div><br></div>
</blockquote></div>
</div></div></blockquote></div><br></div>
</blockquote></div>