Re: [lldb-dev] LLDB Website is not being updated

[Tanya Lattner via lldb-dev]

I’ll have to check the status of moving the scripts over and what is going on. 
But yes, this is all related to moving to GitHub and modifying scripts that 
used to be either on a post-commit hook or nightly cron.

-Tanya

> On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere  wrote:
> 
> I see a bunch of eros here:
> http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html
> 
> Is this possibly related to the Github/monorepo transition?
> 
> -- Jonas
> 
> On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
>  wrote:
>> 
>> Hello Tanya,
>> 
>> it looks like the cron job that is supposed to be updating the LLDB website 
>> isn't running or is otherwise blocked at the moment. You can see on 
>> https://lldb.llvm.org that it says "Welcome to the LLDB version 8 
>> documentation!". We also recently removed the "Why a New Debugger?" headline 
>> and that change isn't showing up either.
>> 
>> Would you mind taking a look?
>> 
>> thanks for your help,
>> Adrian
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Inconsistencies in CIE pointer in FDEs in .debug_frame

[Martin Storsjö via lldb-dev]

Hi,

I'm looking into something that seems like an inconsistency in handling of 
the CIE pointer in FDEs in .debug_frame, between how debug info is 
generated in LLVM and consumed in LLDB.


For FDEs in .eh_frame, the CIE pointer/cie_id field is interpreted as an 
offset from the current FDE - this seems to be consistent.


But for cases in .debug_frame, they are treated differently. In LLDB, the 
cie_id field is assumed to be relative to the begin of the .debug_frame 
section: 
https://github.com/llvm/llvm-project/blob/master/lldb/source/Symbol/DWARFCallFrameInfo.cpp#L482-L495


However, when this field is produced in LLVM, it can, depending on 
MCAsmInfo flags, end up written as a plain absolute address to the CIE: 
https://github.com/llvm/llvm-project/blob/master/llvm/lib/MC/MCDwarf.cpp#L1699-L1705


That code in MCDwarf.cpp hasn't been touched in many years, so I would 
expect that the info it generates actually has been used since and been 
found to be correct. Or are most cases built with -funwind-tables 
or similar, enabled by default?, so this is exercised in untested cases?


In the case where I'm running in this, LLDB reports "error: Invalid cie 
offset" when running executables with such .debug_frame sections.


By adding an ", true" to the end of the EmitSymbolValue call in 
MCDwarf.cpp, the symbol reference is made section relative and the code 
seems to do what LLDB expects. Is that correct, or should LLDB learn the 
cases (which?) where the cie_id is an absolute address instead of a 
section relative one?


// Martin

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev