Struct lldb::SBAddress[][src]

pub struct SBAddress {
    pub raw: SBAddressRef,
}
Expand description

A section + offset based address class.

The SBAddress class allows addresses to be relative to a section that can move during runtime due to images (executables, shared libraries, bundles, frameworks) being loaded at different addresses than the addresses found in the object file that represents them on disk. There are currently two types of addresses for a section:

  • file addresses
  • load addresses

File addresses represents the virtual addresses that are in the ‘on disk’ object files. These virtual addresses are converted to be relative to unique sections scoped to the object file so that when/if the addresses slide when the images are loaded/unloaded in memory, we can easily track these changes without having to update every object (compile unit ranges, line tables, function address ranges, lexical block and inlined subroutine address ranges, global and static variables) each time an image is loaded or unloaded.

Load addresses represents the virtual addresses where each section ends up getting loaded at runtime. Before executing a program, it is common for all of the load addresses to be unresolved. When a DynamicLoader plug-in receives notification that shared libraries have been loaded/unloaded, the load addresses of the main executable and any images (shared libraries) will be resolved/unresolved. When this happens, breakpoints that are in one of these sections can be set/cleared.

Fields

raw: SBAddressRef

The underlying raw SBAddressRef.

Implementations

Construct a new Some(SBAddress) or None.

Check whether or not this is a valid SBAddress value.

Construct a new SBAddress from the given section and offset.

Create a new SBAddress from the given load address within the target.

The address that represents the address as it is found in the object file that defines it.

The address as it has been loaded into memory by a target.

Get the SBSymbolContext for a given address.

An address might refer to code or data from an existing module, or it might refer to something on the stack or heap. This will only return valid values if the address has been resolved to a code or data address using SBAddress::from_load_address or SBTarget::resolve_load_address.

  • resolve_scope: Flags that specify what type of symbol context is needed by the caller. These flags have constants starting with SYMBOL_CONTEXT_ITEM_.

Get the SBModule for a given address.

An address might refer to code or data from an existing module, or it might refer to something on the stack or heap. This will only return valid values if the address has been resolved to a code or data address using SBAddress::from_load_address or SBTarget::resolve_load_address.

This grabs an individual object for a given address and is less efficient if you want more than one symbol related objects. Use one of the following when you want multiple debug symbol related objects for an address:

One or more bits from the SymbolContextItem enumerations can be logically OR’ed together to more efficiently retrieve multiple symbol objects.

Get the SBCompileUnit for a given address.

An address might refer to code or data from an existing module, or it might refer to something on the stack or heap. This will only return valid values if the address has been resolved to a code or data address using SBAddress::from_load_address or SBTarget::resolve_load_address.

This grabs an individual object for a given address and is less efficient if you want more than one symbol related objects. Use one of the following when you want multiple debug symbol related objects for an address:

One or more bits from the SymbolContextItem enumerations can be logically OR’ed together to more efficiently retrieve multiple symbol objects.

Get the SBFunction for a given address.

An address might refer to code or data from an existing module, or it might refer to something on the stack or heap. This will only return valid values if the address has been resolved to a code or data address using SBAddress::from_load_address or SBTarget::resolve_load_address.

This grabs an individual object for a given address and is less efficient if you want more than one symbol related objects. Use one of the following when you want multiple debug symbol related objects for an address:

One or more bits from the SymbolContextItem enumerations can be logically OR’ed together to more efficiently retrieve multiple symbol objects.

Get the SBBlock for a given address.

An address might refer to code or data from an existing module, or it might refer to something on the stack or heap. This will only return valid values if the address has been resolved to a code or data address using SBAddress::from_load_address or SBTarget::resolve_load_address.

This grabs an individual object for a given address and is less efficient if you want more than one symbol related objects. Use one of the following when you want multiple debug symbol related objects for an address:

One or more bits from the SymbolContextItem enumerations can be logically OR’ed together to more efficiently retrieve multiple symbol objects.

Get the SBSymbol for a given address.

An address might refer to code or data from an existing module, or it might refer to something on the stack or heap. This will only return valid values if the address has been resolved to a code or data address using SBAddress::from_load_address or SBTarget::resolve_load_address.

This grabs an individual object for a given address and is less efficient if you want more than one symbol related objects. Use one of the following when you want multiple debug symbol related objects for an address:

One or more bits from the SymbolContextItem enumerations can be logically OR’ed together to more efficiently retrieve multiple symbol objects.

pub fn line_entry(&self) -> Option<SBLineEntry>

Get the SBLineEntry for a given address.

An address might refer to code or data from an existing module, or it might refer to something on the stack or heap. This will only return valid values if the address has been resolved to a code or data address using SBAddress::from_load_address or SBTarget::resolve_load_address.

This grabs an individual object for a given address and is less efficient if you want more than one symbol related objects. Use one of the following when you want multiple debug symbol related objects for an address:

One or more bits from the SymbolContextItem enumerations can be logically OR’ed together to more efficiently retrieve multiple symbol objects.

Trait Implementations

Returns a copy of the value. Read more

Performs copy-assignment from source. Read more

Formats the value using the given formatter. Read more

Executes the destructor for this type. Read more

Performs the conversion.

This method tests for self and other values to be equal, and is used by ==. Read more

This method tests for !=.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Performs the conversion.

Performs the conversion.

The resulting type after obtaining ownership.

Creates owned data from borrowed data, usually by cloning. Read more

🔬 This is a nightly-only experimental API. (toowned_clone_into)

recently added

Uses borrowed data to replace owned data, usually by cloning. Read more

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.