Address relative to the imagebase where the binary's code starts.

Address relative to the imagebase where the binary's data starts. <div class="warning">This value is not present for PE64 files</div>

0xFFFF means not available

Return list of [`X509`] certificates associated with this signature

Clear the content of this segment

Return the data directories as an iterator over the [`DataDirectory`] structure

Return the signature created by the signing certificate's private key

Get the integer value at the given virtual address

Return the segment from the given name

Check if we have at least GLIBC 2.17 (2012)

Index of the first symbol in the group of undefined external symbols.

The initial protections of this segment

Check if the relocation uses the explicit [`Relocation::addend`] field (this is usually the case for 64 bits binaries)

According to the PE specifications, this value is *reserved* and **should** be 0.

The major version number of the image

The minor version number of the image

The linker minor version

The **minor** version number of the required operating system

The minor version number of the subsystem

Number of symbols in the group of local symbols.

Number of entries in the module table. This field seems unused by recent Mach-O loader and should be set to 0

No longer used in recent PE binaries produced by Visual Studio

Function start address

ELF Section index associated with the symbol

Return an iterator over the PE's Section

Set the stack offset of this variable. This function set the `DW_AT_location` attribute

@see Symbol::section_idx

Sign the binary with an ad-hoc signature

Iterator over the signer [`SignerInfo`] defined in the PKCS #7 signature

The size of the code `.text` section or the sum of all the sections that contain code (i.e. sections with `CNT_CODE` flag)

The size of the initialized data which are usually located in the `.data` section. If the initialized data are split across multiple sections, it is t

The size of the uninitialized data which are usually located in the `.bss` section. If the uninitialized data are split across multiple sections, it i

Return the type of the note. This type does not match the `NT_` type value. For accessing the original `NT_` value, check original_type()

Symbol visibility

According to the official PE specifications, this value is reserved and **should** be 0.

Currently BinaryNinja is not aware of RVA (i.e. creating the associated xref/symbols) as Ghidra does but in the future this could change so let make a

Add the given dynamic entry and return the new entry

The location to receive the TLS index assigned by the loader. This location should be located in a writable section like `.data`

Compute the authentihash for the current PE with the given algorithms.

The total number of bytes in the base relocation block. `block_size = sizeof(BaseRelocationBlock) + nb_of_relocs * sizeof(uint16_t = RelocationEntry)`

[`X509`] certificate used by this signer.

RVA to the array that describes architecture-specific ranges

Number of entries in the code map

Return the code page that is used to decode code point values within the resource data. Typically, the code page is the unicode code page.

Number of 32-bit words needed to contain all of the unwind codes

Iterator over the CompilationUnit from the PDB's DBI stream. [`crate::pdb::CompilationUnit`] are also named "Module" in the PDB's official documentati

The beginning of the encrypted area

Raw value

Disassemble code at the given virtual address ``` let insts = binary.disassemble_address(0xacde); for inst in insts { println!("{}", inst.to_string()

Some characteristics of the underlying binary like the support of the PIE. The prefix ``dll`` comes from the official PE specifications but these char

The section index of the dynamic value relocation table

Iterator over the exception (`_RUNTIME_FUNCTION`) functions This function requires that the option [`ParserConfig::parse_exceptions`] was turned on (

RVA to this architecture-specific exception table