ff4ff35918
Red Bear OS is a full fork. All sources must be available from git clone with zero network access. Removed gitignore rules that excluded fetched source trees under recipes/*/source/, local/recipes/kde/*/source/, local/recipes/qt/*/source/, and vendor source trees. Build artifacts (target/, build/, source.tar, *.o, *.so) remain excluded. 127291 files added — kernel, relibc, base, bootloader, pkgar, all KDE/Qt frameworks, mesa, wayland, DRM drivers, and every other recipe source.
35 lines
1.5 KiB
Plaintext
35 lines
1.5 KiB
Plaintext
@c This file contains the entry for the --ctf, --ctf-parent, --ctf-symbols, -and
|
|
@c --ctf-strings options that are common to both readelf and objdump.
|
|
|
|
@item --ctf[=@var{section}]
|
|
@cindex CTF
|
|
@cindex Compact Type Format
|
|
|
|
Display the contents of the specified CTF section. CTF sections themselves
|
|
contain many subsections, all of which are displayed in order.
|
|
|
|
By default, display the name of the section named @var{.ctf}, which is the
|
|
name emitted by @command{ld}.
|
|
|
|
@item --ctf-parent=@var{member}
|
|
|
|
If the CTF section contains ambiguously-defined types, it will consist
|
|
of an archive of many CTF dictionaries, all inheriting from one
|
|
dictionary containing unambiguous types. This member is by default
|
|
named @var{.ctf}, like the section containing it, but it is possible to
|
|
change this name using the @code{ctf_link_set_memb_name_changer}
|
|
function at link time. When looking at CTF archives that have been
|
|
created by a linker that uses the name changer to rename the parent
|
|
archive member, @option{--ctf-parent} can be used to specify the name
|
|
used for the parent.
|
|
|
|
@item --ctf-parent-section=@var{section}
|
|
|
|
This option lets you pick a completely different section for the CTF
|
|
parent dictionary containing unambiguous types than for the child
|
|
dictionaries that contain the ambiguous remainder. The linker does
|
|
not emit ELF objects structured like this, but some third-party linkers
|
|
may. It's also convenient to inspect CTF written out as multiple raw
|
|
files to compose them with objcopy, which can put them in different
|
|
ELF sections but not in different members of a single CTF dict.
|