search for: dwarfdataextractor

On 28/01/2020 20:37, David Blaikie via llvm-dev wrote: > and one idea I had was to have the DWARFDataExtractor return a new > DWARFDataExtractor that was specifically bounded to the parsed length > for this reason. I think this would be great. In fact, I was getting ready to propose something like that myself. :) FWIW, lldb DataExtractors already support this kind of slicing. pl

...keleyText(llvm::object::DataRefImpl) const (ObjectFile.cpp:80) by 0x5538CF9: llvm::object::RelocationRef::getType() const (ObjectFile.h:543) by 0x55AE53E: llvm::object::resolveARM(llvm::object::RelocationRef, unsigned long, unsigned long) (RelocationResolver.cpp:250) by 0x502802B: llvm::DWARFDataExtractor::getRelocatedValue(unsigned int, unsigned int*, unsigned long*) const (DWARFDataExtractor.cpp:27) by 0x5071C2F: llvm::DWARFUnitHeader::extract(llvm::DWARFContext&, llvm::DWARFDataExtractor const&, unsigned int*, llvm::DWARFSectionKind, llvm::DWARFUnitIndex const*, llvm::DWARFUnitIndex::...

...ate constructor (the implicit default constructor) not viable: > requires 0 arguments, but 1 was provided > /home/yawmoo/Desktop/clfs/sources/llvm/tools/lld/ELF/InputFiles.cpp:89:34: error: > no viable conversion from 'llvm::DataExtractor' to 'const > llvm::DWARFDataExtractor' > DwarfLine->getOrParseLineTable(LineData, 0); > ^~~~~~~~ > /home/yawmoo/Desktop/clfs/sources/llvm/include/llvm/DebugInfo/DWARF/DWARFDataExtractor.h:20:7: note: > candidate constructor (the implicit copy constructor) not viable: cannot &g...

...rf.getDWARFObj().getLineSection().Data; LineData.slice(*StmtList + 4, PrologueEnd) ... StringRef FrameData = OrigDwarf.getDWARFObj().getFrameSection().Data; FrameData.substr(EntryOffset, InitialLength + 4) ... InputSec = Dwarf.getDWARFObj().getLocSection(); InputSec.Data.substr(Offset, Length); ... DWARFDataExtractor RangesData(Context.getDWARFObj(), *RangeSection,                               isLittleEndian, getAddressByteSize()); uint64_t ActualRangeListOffset = RangeSectionBase + RangeListOffset; RangeList.extract(RangesData, &ActualRangeListOffset); i.e. It is possible to access random piece of DWAR...

On Mon, 27 Jan 2020 at 23:22, David Blaikie <dblaikie at gmail.com> wrote: > Thanks for all the work & context, James! > Thanks for the reviews! > > On Mon, Jan 27, 2020 at 5:51 AM James Henderson < > jh7370.2008 at my.bristol.ac.uk> wrote: > >> Hi all, >> >> Since December, I've made several changes to the DWARF debug line parser

Hi folks, I am trying to implement the C bindings API for DebugInfo::DWARF::DWARFDie. My goal is to have a C library that reads and parses DWARF debugging format (just like how llvm-dwarfdump does, but maybe more than just dumping debug info) I've started with creating C structure for DebugInfo::DWARF::DWARFContext which contains all DWARF DIEs in the object file. For this I used ```

The bottom of the bug has the revision numbers (e.g. D34035). That one corresponds to e.g. https://reviews.llvm.org/D34035 There's also https://reviews.llvm.org/D34634 which contains all of Peter's patches, but it's not going to rebase cleanly once the individual patches start going in. On 6/28/17, 10:56 AM, "Alessandro Pistocchi" <apukfreelance at gmail.com> wrote:

Hi James, On 05.11.2020 17:59, James Henderson wrote: > (Resending with history trimmed to avoid it getting stuck in moderator > queue). > > Hi Alexey, > > Just an update - I identified the cause of the "Generated debug info > is broken" error message when I tried to build things locally: the > `outStreamer` instance is initialised with the host Triple,