Skip to content

release symbols: dump_syms logged a CFI error and still stored the symbol file #364

Closed

Description

@mubeda

Two Native desktop - macOS arm64 runs on main logged an error from the symbol dump and then stored the archive as if it were complete:

  • 2026-11-06, run 42306937978: [ERROR] CFI: CfiError { kind: BadDebugInfo, source: Some(UnknownVersion(0)) }
  • 2026-11-07, run 42332978679: CFI: CfiError { kind: BadDebugInfo, source: Some(OffsetOutOfBounds(3005218816)) }

The three later arm64 logs that were checked (2026-11-09 and 2026-11-13) have no such line.

To do: find out whether the stored .sym file lacks unwind (CFI) records when this happens, and make scripts/dump-symbols.ts fail, or verify the output, when dump_syms reports an error. Whether a release was built from an affected run was not checked.

Found while diagnosing #359.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions