elf_binaries

elf_section_type(Name:symbol, Code:unsigned)

This module defines predicates and rules specific of ELF binaries

Used by: data_section, function_pointer_section

elf_pointer_array_section_type(SectionTypeName:symbol)

ELF section types that contain an array of code pointers.

Used by: function_pointer_section

plt_section(name:symbol)

got_section(name:symbol)

plt_entry(EA:address, function:symbol)

There is a PLT jump at address ‘EA’ to external function ‘Function’.

Uses: arch.jump, arch.load_operation, arch.reg_arithmetic_operation, best_ifunc_symbol, got_reference_pointer, hi_load, indirect_jump, instruction, instruction_get_op, instruction_get_src_op, loaded_section, next, op_indirect, op_indirect_mapped, op_regdirect_contains_reg, pc_relative_jump, plt_entry_arm_candidate, plt_entry_candidate, plt_section, reg_jump, relocation, symbol

Used by: resolved_transfer, resolved_transfer_to_symbol

Recursive: cmp_defines, first_block_in_byte_interval, overlapping_instruction, split_load_for_symbolization, relocation_adjustment, call_tls_get_addr, simple_data_access_pattern, reg_def_use.def_used, base_relative_operand, split_load_total_points, block, litpool_confidence, reg_has_got, value_reg_limit, stack_def_use.live_var_used, split_load_point, split_load_operand, flags_and_jump_pair, wis_schedule_iter, unresolved_interval, code_in_block, compare_and_jump_indirect_op_valid, __agg_subclause3, inferred_main_in_reg, reg_used_for, is_padding, resolved_reaches, compare_and_jump_indirect, __agg_subclause2, padding_block_candidate, reg_reg_arithmetic_operation_defs, def_used_for_address, impossible_block, plt_block, arm_jump_table_block_instruction, composite_data_access, possible_target_from, jump_table_candidate_refined, base_relative_operation, split_load, __agg_single3, reg_has_base_image, no_value_reg_limit, relative_address_start, wis_schedule, plt_entry, reg_def_use.used_in_block, adjusts_stack_in_block, possible_target, initialized_data_segment, reg_def_use.live_var_at_block_end, cmp_reg_to_reg, indefinite_litpool_ref, negative_block_heuristic, contains_implausible_instr_seq, indexed_pc_relative_load, next_block_in_byte_interval, code_in_block_candidate, symbolic_expr_from_relocation, unlikely_have_symbolic_immediate, incomplete_block, arm_jump_table_data_block_limit, inferred_main_dispatch, arch.simple_data_load, data_block_limit, block_total_points, invalid_jump_table_candidate, stack_def_use.live_var_def, reg_def_use.live_var_def, arm_jump_table_block_start, block_overlap, stack_base_reg_move, may_fallthrough, __agg_single2, block_heuristic, __agg_subclause9, block_implies_block, segment_target_range, stack_def_use.live_var_at_prior_used, cinf_ldr_add_pc, no_return_call_propagated, unresolved_block_overlap, jump_table_max, common_tail, unresolved_interval_order, tls_get_addr, block_points_proportional, likely_fallthrough, block_boundaries, jump_table_element_access, block_points, invalid, jump_table_target, reg_def_use.used, arm_jump_table_candidate, reg_def_use.live_var_at_prior_used, no_return_call, arm_jump_table_skip_first_entry, stack_def_use.defined_in_block, split_load_conflict, arm_jump_table_candidate_start, stack_def_use.live_var_at_block_end, reg_def_use.last_def_in_block, arm_jump_table_cmp_limit, data_in_code, candidate_block_is_not_padding, inter_procedural_edge, known_block, instruction_memory_access_size, overlap_with_litpool, block_limit, function_inference.function_entry_initial, init_symbol_minus_symbol_candidate_arm, const_value_reg_used, self_contained_segment, stack_def_use.last_def_in_block, must_fallthrough, straight_line_last_def, padding_block_limit, jump_table_candidate, no_return_call_refined, block_candidate_dependency_edge, split_load_candidate, stack_def_use.block_last_def, last_value_reg_limit, relative_address, no_return_block, litpool_ref, symbol_minus_symbol_litpool_access_pattern, block_last_instruction, gp_relative_operand, data_in_code_propagate, block_candidate_boundaries, basic_target, compare_and_jump_immediate, wis_memo, __agg_subclause6, nop_in_padding_candidate, reg_def_use.defined_in_block, __agg_single6, relocation_adjustment_total, candidate_block_is_padding, wis_prior, reg_def_use.live_var_used, __agg_subclause7, wis_has_prior, compare_and_jump_register, block_instruction_next, arm_jump_table_data_block, value_reg, contains_plausible_instr_seq, relative_jump_table_entry_candidate, adrp_used, stack_def_use.def_used, got_relative_operand, __agg_subclause10, value_reg_edge, arch.reg_relative_load, reg_def_use.flow_def, hi_load_prop, jump_table_start, branch_to_calculated_pc_rel_addr, tls_desc_call, discarded_block, stack_def_use.live_var_used_in_block, data_segment, value_reg_unsupported, block_next, discarded_split_load, indexed_pc_relative_load_relative, litpool_symbolic_operand, data_block_candidate, reg_def_use.return_block_end, code_in_block_candidate_refined, after_end, jump_table_signed, reg_def_use.block_last_def, base_relative_jump, unresolved_interval_best_block, straight_line_def_used, unresolved_block, data_access, correlated_live_reg, jump_table_prelude, litpool_boundaries, init_ldr_add_pc, arch.extend_load, stack_def_use.used_in_block, stack_def_use.ref_in_block, reg_def_use.ref_in_block, reg_def_use.return_val_used

get_pc_thunk(EA:address, Reg:register)

cie_entry(CieAddr: address, Length:unsigned, CodeAlignmentFactor:unsigned, DataAlignmentFactor:number)

A CIE can be associated to multiple FDEs and it contains information common to all of them. ‘CieAddr’ uniquely identifies the CIE.

Used by: cfi_directive, fde_instruction_ref, last_fde, moved_pc_relative_candidate, symbol_minus_symbol

cie_encoding(CieAddr: address, FdeEncoding:unsigned, LsdaEncoding:unsigned)

cie_encoding complements cie_entry and defines the encodings of the pointers in the FDEs and in the LSDAs associated to this CIE.

Used by: cfi_directive, symbol_minus_symbol, symbol_special_encoding, symbolic_data

cie_personality(CieAddr:address, Personality:address, PersonalityPos:address, PersonalitySize:unsigned, Encoding:unsigned)

The personality routine associated to a CIE entry. This is the procedure that takes care of unwinding the stack and exceptions. For C++ it is typically: ‘__gxx_personality_v0’.

Used by: cfi_directive, labeled_ea, symbol_special_encoding, symbolic_data

fde_entry(FdeAddr: address, Length:unsigned, Cie:address, Start:address, End:address, Lsda:address)

A FDE entry defines how stack unwinding is done in a region of code from ‘start’ to ‘end’. Each FDE points to a parent CIE that contains properties common to multiple FDEs. ‘FdeAddr’ and ‘Length’ determine the location of the FDE entry in the eh_frame section. A FDE entry can have ‘Lsda’ associated that contains exception handling information.

Used by: cfi_directive, endproc_local_index, fde_addresses, fde_block_addresses, fde_instruction_ref, labeled_ea, last_fde, moved_pc_relative_candidate, symbol_minus_symbol, symbol_special_encoding, symbolic_data

fde_pointer_locations(addr:address, startLocation:address, endLocation:address, endSize:unsigned, lsdaLocation:address, lsdaSize:unsigned)

Ancillary predicate that specifies the actual locations of the symbolic expressions in the FDE entry.

Used by: symbol_minus_symbol, symbol_special_encoding, symbolic_data

fde_instruction(FdeAddr:address, Index:unsigned, Size:unsigned, InsnAddr:address, Insn:symbol, Op1:number, Op2:number)

The instructions for stack unwinding are encoded into a dwarf program formed by a list of instructions. Each FDE corresponds to a region in the code and it has its own program. This predicate captures one instruction in that program.

FdeAddr is the address of the FDE and indentifies it uniquely.
Index identifies the instruction within the FDE uniquely.
Size is the size of the instruction in bytes.
InsnAddr is the address where the instruction is located
Insn is the actual opcode of the instruction
Op1 and Op2 are the operands of the instruction.

Used by: cfi_directive, fde_instruction_ref, last_fde_instruction, symbol_minus_symbol

lsda(lsdaAddress:address, callsiteTable:address, callsiteTableEncoding:unsigned, callSiteTableLength:unsigned, typeTable:address, typeTableEncoding:unsigned, landingPadBaseAddress: address)

A LSDA defines the exception information of a region of code (typically a procedure). This is located in section ‘.gcc_except_table’. A LSDA entry contains two main elements a callsite table (see lsda_callsite) and a type table (see lsda_type_entry).

Used by: lsda_symbol_minus_symbol, symbol_special_encoding, symbolic_data

lsda_pointer_locations(lsdaAddress:address, typeTablePointerLocation:address, callsiteTablePointerLoc:address)

Complementary predicate with the locations of the various pointers in a LSDA used for symbolization.

Used by: lsda_symbol_minus_symbol, symbol_special_encoding

lsda_callsite(CallSiteTable_address:address, EA_start:address, Start:address, EA_end:address, End:address, EA_landingPad:address, LandingPad:address, EA_endLandindPad:address)

The range [Start,End) corresponds to the try block and ‘LandingPad’ to the location where the catch block is located. ‘EA_start’, ‘EA_end’ and ‘EA_landingPad’ a the locations of the symbolic expressions in the .gcc_except_table that point to ‘Start’, ‘End’ and ‘LandingPad’ respectively.

Used by: boundary_sym_expr, lsda_callsite_addresses, lsda_symbol_minus_symbol, symbol_special_encoding

lsda_type_entry(lsdaTypeTableAddress:address, index:unsigned, address:address)

The exception handling mechanism chooses which catch block catches an given exception based on the type of the exception. This is done by having references to the types which are encoded in the type table. A lsda_type_entry is an entry in the type table. The “type” is represented as a symbolic expression pointing to ‘address’.

Used by: lsda_symbol_minus_symbol, symbolic_data

arm_exidx_entry(FunctionStart:address, CantUnwind:unsigned)

Address where a function starts according to the ARM exidx table.

This address does not set the low bit for Thumb functions.

Used by: basic_target, block_limit, impossible_block, known_block, negative_block_heuristic

fde_addresses(start:address, end:address)

misaligned_fde_start(start:address, start_adjusted:address)

FDE start points can on occasion be misaligned with the actual start of the function. This has been seen on glibc restore_rt which generates code as follows:

.text .align 16 __restore_rt:

movl $15, %rax syscall

Uses: fde_addresses, instruction, next

Used by: basic_target, fde_block_addresses, known_block

lsda_callsite_addresses(Start:address, End:address, LandingPad:address)

special_encoding(Code:unsigned, Name:symbol)