Re: [lldb-dev] lldb status at windows
yes. i doing it. you can see what clang use d:\\code\\llvm\\build\\bin\\
lld-link.exe
but anyway it is hang :(
2016-01-22 23:30 GMT+03:00 Zachary Turner :
> Under llvm/tools also checkout lld. So your directories should look like
> this:
>
> llvm
> \-- tools
> \-- clang
> \-- lldb
> \-- lld
>
> 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.
>
> On Fri, Jan 22, 2016 at 12:22 PM Red Skotina
> wrote:
>
>> 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
Re: [lldb-dev] lldb status at windows
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.
On Sat, Jan 23, 2016 at 12:51 AM Red Skotina wrote:
> yes. i doing it. you can see what clang use d:\\code\\llvm\\build\\bin\\
> lld-link.exe
> but anyway it is hang :(
>
> 2016-01-22 23:30 GMT+03:00 Zachary Turner :
>
>> Under llvm/tools also checkout lld. So your directories should look like
>> this:
>>
>> llvm
>> \-- tools
>> \-- clang
>> \-- lldb
>> \-- lld
>>
>> 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.
>>
>> On Fri, Jan 22, 2016 at 12:22 PM Red Skotina
>> wrote:
>>
>>> 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
Re: [lldb-dev] lldb status at windows
same.
d:\code\Unity_Unpacker\tests\test2>clang -g -fuse-ld=lld main.cpp
d:\code\Unity_Unpacker\tests\test2>lldb a.exe
(lldb) target create "a.exe"
Current executable set to 'a.exe' (i686).
(lldb) run
Process 6984 launching
---
hangs
2016-01-23 11:54 GMT+03:00 Zachary Turner :
> 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.
>
>
>
> On Sat, Jan 23, 2016 at 12:51 AM Red Skotina
> wrote:
>
>> yes. i doing it. you can see what clang use d:\\code\\llvm\\build\\bin\\
>> lld-link.exe
>> but anyway it is hang :(
>>
>> 2016-01-22 23:30 GMT+03:00 Zachary Turner :
>>
>>> Under llvm/tools also checkout lld. So your directories should look
>>> like this:
>>>
>>> llvm
>>> \-- tools
>>> \-- clang
>>> \-- lldb
>>> \-- lld
>>>
>>> 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.
>>>
>>> On Fri, Jan 22, 2016 at 12:22 PM Red Skotina
>>> wrote:
>>>
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");
>>
Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged
Two libc++ tests fail on 64bit Fedora 23, get_monthname and
get_monthname_wide. Test suite looks good.
On Fri, Jan 22, 2016 at 10:09 PM, Nikola Smiljanic
wrote:
> Something is failing on 32bit Fedora 23 (compiler-rt?), test suite looks
> good.
>
> On Fri, Jan 22, 2016 at 2:52 PM, Brian Cain via cfe-dev <
> cfe-...@lists.llvm.org> wrote:
>
>> On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier wrote:
>>
>>>
>>> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev <
>>> cfe-...@lists.llvm.org> wrote:
>>>
SuSE Linux Enterprise Server 11SP3 x86_64
Looks like I see several failures that weren't in 3.7.1. Is there any
way to tell whether these are regressions vs new-to-3.8.0-but-failing? The
MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were
not in 3.7.1.
>>> All of the libc++ failures seem like non-issues and should be in 3.7.1.
>>> Did you change or upgrade your platform or libc version? I'm not sure
>>> about the libc++abi error though.
>>>
>>
>> I don't recall any changes to libc. Attached is the testing log from
>> 3.7.1 rc2 (I don't have logs from -final handy).
>>
>> I can repeat a 3.7.1 release build on this system now. I don't think the
>> results will change, though.
>>
>>
>>
>>>
Failing Tests (27):
LLVM-Unit :: Support/SupportTests/ThreadPoolTest.Async
LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrier
LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrierArgs
LLVM-Unit :: Support/SupportTests/ThreadPoolTest.GetFuture
LLVM-Unit :: Support/SupportTests/ThreadPoolTest.PoolDestruction
MemorySanitizer :: Linux/obstack.cc
MemorySanitizer :: Linux/process_vm_readv.cc
MemorySanitizer :: fork.cc
MemorySanitizer :: iconv.cc
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.fgetgrent_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent_r
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getpwent
MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getpwent_r
MemorySanitizer-Unit ::
Msan-x86_64-with-call-Test/MemorySanitizer.fgetgrent_r
MemorySanitizer-Unit ::
Msan-x86_64-with-call-Test/MemorySanitizer.getgrent
MemorySanitizer-Unit ::
Msan-x86_64-with-call-Test/MemorySanitizer.getgrent_r
MemorySanitizer-Unit ::
Msan-x86_64-with-call-Test/MemorySanitizer.getpwent
MemorySanitizer-Unit ::
Msan-x86_64-with-call-Test/MemorySanitizer.getpwent_r
SanitizerCommon-Unit ::
Sanitizer-x86_64-Test/SanitizerLinux.ThreadDescriptorSize
ThreadSanitizer :: Linux/mutex_robust.cc
ThreadSanitizer :: Linux/mutex_robust2.cc
ThreadSanitizer :: thread_name2.cc
libc++ :: std/depr/depr.c.headers/uchar_h.pass.cpp
>>>
>>> This is caused because the system does not provide a uchar.h header.
>>>
>>>
libc++ ::
std/localization/locale.categories/category.time/locale.time.get.byname/get_monthname.pass.cpp
libc++ ::
std/localization/locale.categories/category.time/locale.time.get.byname/get_monthname_wide.pass.cpp
>>>
>>>
>>> These are marked XFAIL on open-suse, They should probably be marked as
>>> XFAIL on your platform as well.
>>> Can you send me the output of Python's "platform.linux_distribution()"?
>>>
>>>
>>
>> Ok, I'll be able to get this tomorrow. But I suspect it will be "('SUSE
>> Linux Enterprise Server ', '11', 'x86_64')"
>>
>>
>>> libc++abi :: cxa_thread_atexit_test.pass.cpp
>>>
>>> Not sure about this failure. Can you send me the output?
>>>
>>>
>> That one failed in 3.7.1 also. IIRC this libstdc++ doesn't have
>> cxa_thread_atexit.
>>
>> ___
>> cfe-dev mailing list
>> cfe-...@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-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
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. On Sat, Jan 23, 2016 at 12:57 AM Red Skotina wrote: > same. > > d:\code\Unity_Unpacker\tests\test2>clang -g -fuse-ld=lld main.cpp > > d:\code\Unity_Unpacker\tests\test2>lldb a.exe > (lldb) target create "a.exe" > Current executable set to 'a.exe' (i686). > (lldb) run > > Process 6984 launching > --- > hangs > > 2016-01-23 11:54 GMT+03:00 Zachary Turner : > >> 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. >> >> >> >> On Sat, Jan 23, 2016 at 12:51 AM Red Skotina >> wrote: >> >>> yes. i doing it. you can see what clang use d:\\code\\llvm\\build\\bin\\ >>> lld-link.exe >>> but anyway it is hang :( >>> >>> 2016-01-22 23:30 GMT+03:00 Zachary Turner : >>> Under llvm/tools also checkout lld. So your directories should look like this: llvm \-- tools \-- clang \-- lldb \-- lld 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. On Fri, Jan 22, 2016 at 12:22 PM Red Skotina wrote: > 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
Re: [lldb-dev] lldb status at windows
thanks. i will wait 2016-01-23 19:27 GMT+03:00 Zachary Turner : > 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. > > On Sat, Jan 23, 2016 at 12:57 AM Red Skotina > wrote: > >> same. >> >> d:\code\Unity_Unpacker\tests\test2>clang -g -fuse-ld=lld main.cpp >> >> d:\code\Unity_Unpacker\tests\test2>lldb a.exe >> (lldb) target create "a.exe" >> Current executable set to 'a.exe' (i686). >> (lldb) run >> >> Process 6984 launching >> --- >> hangs >> >> 2016-01-23 11:54 GMT+03:00 Zachary Turner : >> >>> 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. >>> >>> >>> >>> On Sat, Jan 23, 2016 at 12:51 AM Red Skotina >>> wrote: >>> yes. i doing it. you can see what clang use d:\\code\\llvm\\build\\bin\\lld-link.exe but anyway it is hang :( 2016-01-22 23:30 GMT+03:00 Zachary Turner : > Under llvm/tools also checkout lld. So your directories should look > like this: > > llvm > \-- tools > \-- clang > \-- lldb > \-- lld > > 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. > > On Fri, Jan 22, 2016 at 12:22 PM Red Skotina > wrote: > >> 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,
Re: [lldb-dev] lldb status at windows
im rebuild lldb as x64 application and reabuild my test application with x64 llvm. at first look same. But when my internet was breaked at some moment application under lldb run and finish correct. It is like some magic with my pc. When i have acces to internet lldb hangs, when i disable my internet - it is correct finished. I try examine this behavior and determine finite conditions for hangs. 2016-01-23 19:27 GMT+03:00 Zachary Turner : > 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. > > On Sat, Jan 23, 2016 at 12:57 AM Red Skotina > wrote: > >> same. >> >> d:\code\Unity_Unpacker\tests\test2>clang -g -fuse-ld=lld main.cpp >> >> d:\code\Unity_Unpacker\tests\test2>lldb a.exe >> (lldb) target create "a.exe" >> Current executable set to 'a.exe' (i686). >> (lldb) run >> >> Process 6984 launching >> --- >> hangs >> >> 2016-01-23 11:54 GMT+03:00 Zachary Turner : >> >>> 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. >>> >>> >>> >>> On Sat, Jan 23, 2016 at 12:51 AM Red Skotina >>> wrote: >>> yes. i doing it. you can see what clang use d:\\code\\llvm\\build\\bin\\lld-link.exe but anyway it is hang :( 2016-01-22 23:30 GMT+03:00 Zachary Turner : > Under llvm/tools also checkout lld. So your directories should look > like this: > > llvm > \-- tools > \-- clang > \-- lldb > \-- lld > > 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. > > On Fri, Jan 22, 2016 at 12:22 PM Red Skotina > wrote: > >> 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\\Tem
