Home
last modified time | relevance | path

Searched refs:SegInfo (Results 1 – 3 of 3) sorted by relevance

/external/valgrind/docs/internals/
Dsegments-seginfos.txt6 SegInfo is from the very original Valgrind code, and so it predates
22 A SegInfo specifically describes memory mmaped from an ELF object file.
24 Segments can point to one Seginfo. A SegInfo can relate to a memory
26 first page of an ELF file (the one containing the header), a SegInfo
29 appears in the address range of an existing SegInfo, it will have that
30 SegInfo attached to it, presumably because its part of a .so file.
32 pieces will still be associated with the same SegInfo. For this reason,
33 the address/length info in a SegInfo is not a duplicate of the Segment
52 > Aha. So the range of a SegInfo will always be equal to or greater
54 > file plus some extra pages, and then the SegInfo won't cover the extra
[all …]
/external/valgrind/coregrind/m_debuginfo/
DREADME.txt16 storage.c contains the SegInfo structure and stuff for
/external/llvm/tools/llvm-objdump/
DMachODump.cpp8742 class SegInfo { class
8744 SegInfo(const object::MachOObjectFile *Obj);
8766 SegInfo::SegInfo(const object::MachOObjectFile *Obj) { in SegInfo() function in SegInfo
8790 StringRef SegInfo::segmentName(uint32_t SegIndex) { in segmentName()
8798 bool SegInfo::isValidSegIndexAndOffset(uint32_t SegIndex, in isValidSegIndexAndOffset()
8812 const SegInfo::SectionInfo &SegInfo::findSection(uint32_t SegIndex, in findSection()
8826 StringRef SegInfo::sectionName(uint32_t SegIndex, uint64_t OffsetInSeg) { in sectionName()
8830 uint64_t SegInfo::address(uint32_t SegIndex, uint64_t OffsetInSeg) { in address()
8837 SegInfo sectionTable(Obj); in printMachORebaseTable()
8881 SegInfo sectionTable(Obj); in printMachOBindTable()
[all …]