Skip to content

ELF_STT_NO_TYPE symbol incorrectly selected for function #8159

@Alkalem

Description

@Alkalem

Version and Platform (required):

  • Binary Ninja Version: 5.4.9597-dev, also 5.3.9434-Stable
  • Edition: Personal
  • OS: Ubuntu Linux
  • OS Version: 25.10
  • CPU Architecture: x64

Bug Description:
Two ELF symbols exist at the same address, one is a local function symbol, the other is a global no-type symbol. The no-type symbol ends up as DataSymbol and FunctionSymbol and is displayed as function name.

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. Open harmony canyon renders monotonically
  2. Observe first function symbol (should be at 0x11800800)
  3. Function name should show as local with correct name briefly, before updating to global stack-end name.

Expected Behavior:
The stack-end symbol marks the end of a data region from a previous section. Although its visibility is global, the type ELF_STT_NO_TYPE should not be applied to a function. A function symbol at the same address exists and should be used instead.

Binary:
harmony canyon renders monotonically

Additional Information:
The bug was initially observed with a TMS320C6x plugin, but the behavior is the same if any other arch is used instead. Only ELF and core symbol handling seem to cause this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions