Skip to content
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

Force gcc to produce DWARF4 so that gdb can use it #607

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

mikebeaton
Copy link
Contributor

Addresses #606.

I am not sure if the location where I have added the flags is ideal, though it does make shim debuggable again.

@supperpiccle
Copy link

I ran into this exact problem and the solution here fixed it.

However, I tested with a version of gdb that supports DWARF 5. Both gdb 12.1 and 13.1 ran into this issue. I suspect it's an issue with this piece in the makefile

%.efi.debug : %.so ifneq ($(OBJCOPY_GTE224),1) $(error objcopy >= 2.24 is required) endif $(OBJCOPY) -D -j .text -j .sdata -j .data \ -j .dynamic -j .rodata -j .rel* \ -j .rela* -j .dyn -j .reloc -j .eh_frame -j .sbat \ -j .sbatlevel \ -j .debug_info -j .debug_abbrev -j .debug_aranges \ -j .debug_line -j .debug_str -j .debug_ranges \ -j .note.gnu.build-id \ $< $@

I don't know anything about the differences between version 4 and 5, but I suspect the objcopy there isn't conforming to whatever specification version 5 requires. Long term, I think the solution would be to run down what's wrong here.

@vathpela vathpela added this to the shim 16 milestone Nov 12, 2024
@vathpela vathpela merged commit 3cf0e09 into rhboot:main Dec 13, 2024
19 checks passed
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.

3 participants