Search results

Page title matches

• Changes/Package information on ELF objects
  = Package information on ELF objects = All binaries (executables and shared libraries) are annotated with an ELF note that identifies the rpm for which this file was built. This allows bin
  28 KB (4,394 words) - 21:18, 13 January 2022

Page text matches

• How to check for ABI changes in a package
  ...ble with the ABI of its previous version. That compatibility ensures that ELF binaries, that [https://en.wikipedia.org/wiki/Linker_%28computing%29 dynami ...the normal update process followed by maintainers of packages that contain ELF libraries.
  2 KB (322 words) - 11:25, 15 August 2017
• Toolchain/Watermark/RealBinarySeparateDebuginfo
  Separate debuginfo has an invalid ELF program header, but it is difficult to recognize at such. We receive occas
  314 bytes (44 words) - 10:35, 24 October 2016
• How to check for ABI changes with abidiff
  ...ps://en.wikipedia.org/wiki/Application_binary_interface ABIs] of two C/C++ ELF binaries. It does so by analyzing the content the ELF binaries themselves, including their debug information. It can pinpoint ABI
  2 KB (382 words) - 08:35, 20 November 2015
• Toolchain
  * [[Toolchain/Watermark|Markup for ELF objects]]
  925 bytes (111 words) - 18:17, 19 November 2018
• Toolchain/Watermark/SystemCalls
  If an object calls Linux system calls directly, it is not visible from its ELF symbols. For a quick check whether a binary is compatible with a certain k
  546 bytes (84 words) - 11:45, 9 November 2016
• How to check for ABI changes with abipkgdiff
  ...es the [https://en.wikipedia.org/wiki/Application_binary_interface ABI] of ELF binaries carried by two versions of a given package. It does so by analyzing the content the ELF binaries themselves, including their debug information. It can pinpoint ABI
  3 KB (445 words) - 09:59, 20 November 2015
• Architectures/RISC-V/64ILP32/zh-cn
  make ARCH=riscv CROSS_COMPILE=<YOUR PATH>/riscv/bin/riscv64-unknown-elf- k230_evb_linux_enable_vector_defconfig all make ARCH=riscv CROSS_COMPILE=<YOUR PATH>/riscv/bin/riscv64-unknown-elf- k230_evb_linux_enable_vector_defconfig 64ilp32.config all
  3 KB (287 words) - 17:45, 5 March 2024
• Toolchain/Watermark/DWARFCoverage
  If DWARF is used for [[Toolchain/Watermarking|ELF object markup]], it is necessary to ensure all code in an object is covered
  587 bytes (87 words) - 10:16, 24 October 2016
• Toolchain/Watermark/PIEDSO
  ...dynamic shared objects (DSOs). Both are marked <code>ET_DYN</code> in the ELF header, so it is not entirely obvious how to tell them apart. Also https://bugzilla.redhat.com/show_bug.cgi?id=1439328 /usr/include/elf.h is behind the times.
  863 bytes (134 words) - 16:21, 27 September 2017
• Changes/.got.plt Isolation
  ...definitely because the relevant standard body did not approve the required ELF changes.}} = Build non-RELRO ELF binaries with .got.plt isolation =
  6 KB (937 words) - 16:50, 24 July 2019
• How to check for ABI changes with abi compliance checker
  == procedure for comparing the ABIs of two ''Elf binaries'' ==
  5 KB (797 words) - 11:19, 15 August 2017
• Architectures/RISC-V/64ILP32
  make ARCH=riscv CROSS_COMPILE=<YOUR PATH>/riscv/bin/riscv64-unknown-elf- k230_evb_linux_enable_vector_defconfig all make ARCH=riscv CROSS_COMPILE=<YOUR PATH>/riscv/bin/riscv64-unknown-elf- k230_evb_linux_enable_vector_defconfig 64ilp32.config all
  4 KB (546 words) - 03:57, 6 March 2024
• Toolchain/Watermark
  == Markup for ELF objects == This project intends to add markers to ELF objects so that it is possible to determine whether they have certain prope
  15 KB (2,404 words) - 09:24, 28 March 2023
• Packaging:Debuginfo
  A useful debuginfo package contains stripped symbols from ELF binaries (<code>*.debug</code> in <code>/usr/lib/debug</code>) as well as t ...nder the hood after the <code>%install</code> section. Make sure that all ELF binaries (executables, shared libraries, DSO's) are executable at end of <c
  6 KB (890 words) - 19:56, 21 December 2018
• Changes/ParallelInstallableDebuginfo
  ...file /usr/lib/debug/.build-id/xx/yyyy...yyy which is a symlink to the main ELF file. ...r/lib/debug/.build-id/xx/yyyy...yyy.debug which is a symlink to the .debug ELF file.
  14 KB (2,305 words) - 16:44, 12 October 2017
• Security Features
  ...and Exec-Shield. The executable binary file on the system is protected by ELF hardening. Finally, SELinux policies are in place so that if httpd is crac == ELF (Executable and Linkable Format) Data Hardening ==
  9 KB (1,388 words) - 01:26, 31 December 2022
• Packaging:C and C++
  A: No. RPM will automatically determine what ELF libraries you need based on the binaries in your package. This is sufficien
  4 KB (582 words) - 03:38, 20 December 2018
• Summer Coding 2010 ideas - Universal Build-ID
  The main idea behind Build-IDs is to make elf files "self-identifying". ...le. Which means that it is unique among the set of meaningful contents for ELF files and identical when the output file would otherwise have been identica
  13 KB (2,217 words) - 09:11, 18 September 2016
• GlibcRawhideSync
  FAIL: elf/tst-debug1 =====FAIL: elf/tst-debug1.out=====
  18 KB (2,742 words) - 19:47, 1 February 2024
• Darkserver
  ...enable their analysis, debugging profiling, by finding out where the rpm / elf / dwarf files may be * elf-utils
  8 KB (1,268 words) - 04:09, 6 January 2021