<div dir="ltr"><div><div><div><div>Results from 'check-all' project:</div><div>-----------------------------------------<br></div><div><br></div><div>Additional requirement: the regression tests requires the python 'psutil' module.</div><div><br></div>There is a common error when trying to build 'check-all' project. One of the instances can be seen on:<br><br>llvm\projects\compiler-rt\<wbr>test\lit.common.cfg:34</div><div><br></div><div># Setup clang binary.<br>compiler_path = getattr(config, 'clang', None)<br>if (not compiler_path) or (not os.path.exists(compiler_path)):<br> lit_config.fatal("Can't find compiler on path %r" % compiler_path)<br><br></div>that generates the following error:<br><br>"Can't find compiler on path <pathname>"<br><br></div>with pathname pointing to the required clang.exe, but having the $(Configuration) string. Basically, that cmake attribute not being expanded. Is was building the 'Release' configuration.<br><br></div>Using the option -DLLVM_BUILD_RUNTIME=OFF, seems to fix the problems. But I do not know about any side effects on the LLDB tests.<br><br><div><div><div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">Carlos</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 19, 2017 at 11:19 AM, Carlos Alberto Enciso <span dir="ltr"><<a href="mailto:international.phantom@gmail.com" target="_blank">international.phantom@gmail.c<wbr>om</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div>I have been trying to build LLDB on Windows (7) and after couple of days, I managed to have a successfull build.<br><br></div>These are my findings:<br><br></div>1) Follow the instructions from<br><br><a href="https://lldb.llvm.org/build.html" target="_blank">https://lldb.llvm.org/build.ht<wbr>ml</a><br><br></div>2) With Python 2.7, the cmake process fails, as it can't locate the following files:<br><br></div>python_d.exe<br></div>python27_d.lib<br></div>python27_d.dll<br><br></div>3) During the installation of Python 3.6, make sure to include the Debug Symbols, which are the missing files from (2).<br><br></div>4) Set the following environment variables:<br><br></div>PYTHONHOME -> Directory where Python 3.6 is installed<br></div>PYTHONPATH=%PYTHONHOME%\Lib <wbr> <- Lib<br></div>PYTHON_INCLUDE=%PYTHONHOME%\In<wbr>clude<br></div>PYTHON_LIB=%PYTHONHOME%\Libs<br><br><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>5) SWIG</div><div><br></div><div>Download the distribution specified in the LLDB documentation:</div><div><br></div><div><a href="http://prdownloads.sourceforge.net/swig/swigwin-3.0.12.zip" target="_blank">http://prdownloads.sourceforge<wbr>.net/swig/swigwin-3.0.12.zip</a></div><div><br></div><div>Unzipp the whole contents and add an environment variable like</div><div><br></div><div>SWIG_DIR -> Directory where the zip file was unzipped.</div><div><br></div><div>It seems that the only way for cmake to pick up some of the previous environment variables, is to specifiy them as parameters in the command line.</div><div><br></div><div>At the end, with the following command line I managed to get a successful build.</div><div><br></div><div>cmake -G "Visual Studio 14 2015 Win64" -DCMAKE_BUILD_TYPE=Release -DSWIG_DIR=C:\ProgramData\SWIG<wbr> -DPYTHON_HOME=C:\ProgramData\P<wbr>ython36 -DPYTHON_EXECUTABLE=C:\Program<wbr>Data\Python36\python.exe ..\llvm</div><div><br></div><div>You can add the following options if needed:</div><div><br></div><div>-DLLDB_TEST_DEBUG_TEST_CRASHES<wbr>=1</div><div>-DLLDB_RELOCATABLE_PYTHON=1</div><div>-DLLDB_TEST_COMPILER=<path to compiler to be used for testing> <br></div><div><br></div><div>My next tasks are:</div><div><br></div><div>try: check-all, check_lldb configurations.</div><div><br></div><div>I will post my findings.</div><div><br></div><div>Hope this help.</div><div><br> </div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On Thu, Sep 14, 2017 at 6:10 PM, John Lindal <span dir="ltr"><<a href="mailto:lldb.jafl@gmail.com" target="_blank">lldb.jafl@gmail.com</a>></span> wrote:<br></span><div><div class="gmail-m_1124222516151370625gmail-m_-6380772402627555765h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Which platform are you building on? I have been unable to build on OS X.<span class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570HOEnZb"><font color="#888888"><div><br></div><div>John</div></font></span><div><div class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570h5"><div><br></div><div><br><div><blockquote type="cite"><div>On Sep 14, 2017, at 10:08 AM, Carlos Alberto Enciso via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:</div><br class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570m_-1099410629221206149Apple-interchange-newline"><div><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><div><div><div>Hi Tamas,<br><br></div>Thanks very much for your reply and the useful information.<br><br></div>In order to properly test my changes (I have another Debug Information ready for submission) I would like be able to build LLDB on my local machine. Once I reach that point, I will follow the process you described (compile calling.cpp) and I would let you know my progress.<br><br></div>Best regards,<br></div>Carlos<br><div><div><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 14, 2017 at 11:20 AM, Tamas Berghammer<span class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570m_-1099410629221206149Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:tberghammer@google.com" target="_blank">tberghammer@google<wbr>.com</a>></span><span class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570m_-1099410629221206149Apple-converted-space"> </span>wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Carlos,<div><br></div><div>Thank your for looking into the LLDB failure. I looked into it briefly and the issue is that we have have 2 function f and g where g is inlined into f as the first call and this causes the first non-prologue line entry of f to be inside the address range of g what means that when we step info f from outside we will end up inside g instead. Previously the first line entry for f matched with the start address of the inlined copy of g where LLDB was able to handle the stepping properly.</div><div><br></div><div>For the concrete example you should compile <a href="https://github.com/llvm-mirror/lldb/blob/26fea9dbbeb3020791cdbc46fbf3cc9d7685d7fd/packages/Python/lldbsuite/test/functionalities/inline-stepping/calling.cpp" target="_blank">https://github.com/llv<wbr>m-mirror/lldb/blob/26fea9dbbeb<wbr>3020791cdbc46fbf3cc9d7685d7fd/<wbr>packages/Python/lldbsuite/test<wbr>/functionalities/inline-steppi<wbr>ng/calling.cpp</a> with "/mnt/ssd/ll/git/build/host-re<wbr>lease/bin/clang-5.0 -std=c++11 -g -O0 -fno-builtin -m32 --driver-mode=g++ calling.cpp" and then observe that caller_trivial_2 have a DW_AT_low_pc = 0x8048790 and the inlined inline_trivial_1 inside it have a DW_AT_low_pc = 0x8048793 but the first line entry after "Set prologue_end to true" is at 0x8048796 while previously it was at 0x8048793.</div><div><br></div><div>Tamas</div><br><div class="gmail_quote"><div><div class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570m_-1099410629221206149m_-1603454934856988710h5"><div dir="ltr">On Thu, Sep 14, 2017 at 9:59 AM Carlos Alberto Enciso via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570m_-1099410629221206149m_-1603454934856988710h5"><div dir="ltr"><div><div><div><div>Hi,<br><br></div>I have been working on a compiler issue, where instructions associated to the function prolog are assigned line information, causing the debugger to show incorrectly the beginning of the function body.<br></div><div><br></div><div>For a full description, please see:<br></div><br><a href="https://reviews.llvm.org/D37625" target="_blank">https://reviews.llvm.org/D3762<wbr>5</a><br><a href="https://reviews.llvm.org/rL313047" target="_blank">https://reviews.llvm.org/rL313<wbr>047</a><br><br></div>The submitted patch caused some LLDB tests to fail. I have attached the log failure.</div><div><br></div><div>I have no knowledge about the test framework used by LLDB.</div><div><br></div><div>What is the best way to proceed in this case?</div><div><br></div><div>Thanks very much for your feedback.</div><div><br></div><div>Carlos Enciso<br></div><div><br><br><div><br></div></div></div></div></div>______________________________<wbr>_________________<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/<wbr>mailman/listinfo/lldb-dev</a><br></blockquote></div></div></blockquote></div><br></div></div></div></div></div></div></div></div></div><div id="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570m_-1099410629221206149DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><table style="border-top:1px solid rgb(211,212,222)"><tbody><tr><td style="width:55px;padding-top:13px"><a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png" alt="" style="width: 46px; height: 29px;" width="46" height="29"></a></td><td style="width:470px;padding-top:12px;color:rgb(65,66,78);font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free.<span class="gmail-m_1124222516151370625gmail-m_-6380772402627555765m_-6108485760828159570m_-1099410629221206149Apple-converted-space"> </span><a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" style="color:rgb(68,83,234)" target="_blank">www.avg.com</a></td></tr></tbody></table><a width="1" height="1"></a></div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline">______________________________<wbr>_________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline">lldb-dev mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline"><a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline"><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/lldb-dev</a></span></div></blockquote></div><br></div></div></div></div></blockquote></div></div></div><br></div>
</blockquote></div><br></div></div></div></div></div>