<div dir="ltr"><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 dir="ltr"><<a href="mailto:tberghammer@google.com" target="_blank">tberghammer@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;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/<wbr>test/functionalities/inline-st<wbr>epping/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="m_-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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-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="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid #d3d4de">
<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="" width="46" height="29" style="width: 46px; height: 29px;"></a></td>
<td style="width:470px;padding-top:12px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank" style="color:#4453ea">www.avg.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>