Skip to content

symcheck: Ignore symbols in .debug_gdb_scripts #1005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 7, 2025

Conversation

tgross35
Copy link
Contributor

@tgross35 tgross35 commented Aug 7, 2025

Since 1, our object files may now contain a GDB script section. These
symbols wind up with multiple instances in the archive but are weak, so
we can safely ignore them in our duplicates check.

This resolves the current CI failures.

@tgross35 tgross35 force-pushed the fix-symcheck branch 2 times, most recently from e0e4fa6 to 9bc253d Compare August 7, 2025 08:23
@tgross35 tgross35 changed the title poke ci symcheck: Ignore symbols in .debug_gdb_scripts Aug 7, 2025
@tgross35 tgross35 marked this pull request as ready for review August 7, 2025 08:32
Currently `SymInfo` stores a `Section`, which is just an index:

    SymInfo {
        section: Section(
            SectionIndex(
                539,
            ),
        ),
        ...
    },

Look up and store the section name instead if possible, with a fallback
to the `Section` debug printing. This makes output more clear and will
allow us to filter by section name.
Since [1], our object files may now contain a GDB script section. These
symbols wind up with multiple instances in the archive but are weak, so
we can safely ignore them in our duplicates check.

This resolves the current CI failures.

[1]: rust-lang/rust#143679
@tgross35 tgross35 merged commit e74519e into rust-lang:master Aug 7, 2025
38 checks passed
@tgross35 tgross35 deleted the fix-symcheck branch August 7, 2025 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant