[Bug binutils/30355] [DWARFv5] readelf: loc_offset XX too big

2023-04-19 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30355 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug binutils/30355] [DWARFv5] readelf: loc_offset XX too big

2023-04-19 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=30355 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=28ab94f51dcdee056d96e57ad04c27c22cf854ea commit 28ab94f51dcdee056d96e57ad04

[Bug binutils/30355] [DWARFv5] readelf: loc_offset XX too big

2023-04-18 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30355 --- Comment #3 from Nick Clifton --- (In reply to Nick Desaulniers from comment #2) > What's the best way to strip out the debug info? > > $ objcopy --only-keep-debug vmlinux vmlinux-debug > $ du -h vmlinux vmlinux-debug > 34M vmlinux > 33

[Bug binutils/30355] [DWARFv5] readelf: loc_offset XX too big

2023-04-17 Thread ndesaulniers at google dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30355 --- Comment #2 from Nick Desaulniers --- $ eu-readelf --debug-dump=info vmlinux 1>/dev/null produced no output to stderr, and the return code was 0. What's the best way to strip out the debug info? $ objcopy --only-keep-debug vmlinux vmlinu

[Bug binutils/30355] [DWARFv5] readelf: loc_offset XX too big

2023-04-17 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30355 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1