Re: nm/objdump --hep still display unsupported styles about --demangle.
Hi nora-pxh, So if you execute --demangle=gnu, it will display error message: unknown demangling style gnu. Would you delete unsupported styles from usage of nm and objdump? Thanks for reporting this problem. The issue has been fixed by commit 0d64622696e0 Cheers Nick
[Bug ld/27442] FAIL: Local ifunc-using executable does not contain R_*_IRELATIVE relocation
https://sourceware.org/bugzilla/show_bug.cgi?id=27442 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #2 from Nick Clifton --- (In reply to dave.anglin from comment #1) Hi Dave, > The attached patch fixes the ifunc test fails on hppa*-*-linux-gnu. > > 1) The regexp in contains_irelative_reloc fails to match upper case letters > arising in symbol names. > 2) tmpdir/static_prog doesn't contain any relocs on hppa, so I skipped test > on hppa. Patch approved - please apply. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/28262] Add warning when generating code in data section
https://sourceware.org/bugzilla/show_bug.cgi?id=28262 Nick Clifton changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #7 from Nick Clifton --- (In reply to Steve Dunnagan from comment #6) > My suggestion is that we not add what might be a nuisance warning. I have to say that I agree. So I am going to close this PR. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28614] [AArch64] opcodes/aarch64-*: -Werror=maybe-uninitialized hit unless assertations are enabled
https://sourceware.org/bugzilla/show_bug.cgi?id=28614 --- Comment #2 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=7060c28edd16a871fe1f8edaa8e49083a39b7ee5 commit 7060c28edd16a871fe1f8edaa8e49083a39b7ee5 Author: Nick Clifton Date: Thu Nov 25 13:11:25 2021 + Fix building the AArch64 assembler and disassembler when assertions are disabled. PR 28614 * aarch64-asm.c: Replace assert(0) with real code. * aarch64-dis.c: Likewise. * aarch64-opc.c: Likewise. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28614] [AArch64] opcodes/aarch64-*: -Werror=maybe-uninitialized hit unless assertations are enabled
https://sourceware.org/bugzilla/show_bug.cgi?id=28614 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||nickc at redhat dot com Resolution|--- |FIXED --- Comment #3 from Nick Clifton --- I am not a fan of using abort() inside a library. In my opinion library calls should never fail. If they cannot complete they should return some kind of error indication and allow their caller to decide what should be done. To that end I have applied my own patch which replaces the assert(0) invocations with "return false" or something similar. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28614] [AArch64] opcodes/aarch64-*: -Werror=maybe-uninitialized hit unless assertations are enabled
https://sourceware.org/bugzilla/show_bug.cgi?id=28614 --- Comment #4 from Pekka Seppänen --- Agreed, that is indeed a better option. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
Issue 39474 in oss-fuzz: binutils:fuzz_readelf: Null-dereference READ with empty stacktrace
Updates: Labels: -restrict-view-commit Comment #4 on issue 39474 by sheriffbot: binutils:fuzz_readelf: Null-dereference READ with empty stacktrace https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=39474#c4 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 41362 in oss-fuzz: binutils:fuzz_disassemble: Dynamic-stack-buffer-overflow in extract_fields
Updates: Labels: -restrict-view-commit Comment #3 on issue 41362 by sheriffbot: binutils:fuzz_disassemble: Dynamic-stack-buffer-overflow in extract_fields https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41362#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 41363 in oss-fuzz: binutils:fuzz_objdump_safe: Dynamic-stack-buffer-overflow in error_handler_internal
Updates: Labels: -restrict-view-commit Comment #4 on issue 41363 by sheriffbot: binutils:fuzz_objdump_safe: Dynamic-stack-buffer-overflow in error_handler_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41363#c4 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 37698 in oss-fuzz: binutils:fuzz_readelf: Abrt with empty stacktrace
Updates: Labels: -restrict-view-commit -deadline-approaching Deadline-Exceeded Comment #3 on issue 37698 by sheriffbot: binutils:fuzz_readelf: Abrt with empty stacktrace https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=37698#c3 This bug has exceeded our disclosure deadline. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 41337 in oss-fuzz: binutils:fuzz_disas_ext-bfd_arch_i386: Dynamic-stack-buffer-overflow in fetch_data
Updates: Labels: -restrict-view-commit Comment #3 on issue 41337 by sheriffbot: binutils:fuzz_disas_ext-bfd_arch_i386: Dynamic-stack-buffer-overflow in fetch_data https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41337#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
[Bug gas/28629] New: [gas, --gdwarf-5] File 0 has wrong dir
https://sourceware.org/bugzilla/show_bug.cgi?id=28629 Bug ID: 28629 Summary: [gas, --gdwarf-5] File 0 has wrong dir Product: binutils Version: 2.38 (HEAD) Status: NEW Severity: normal Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Consider the following compilation: ... $ pwd -P /home/vries/gdb_versions/devel $ as --gdwarf-5 --64 -o tui-layout-asm-short-prog.o /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.S ... First, lets look at the debug info: ... $ readelf -wi tui-layout-asm-short-prog.o Contents of the .debug_info section: Compilation Unit @ offset 0x0: Length:0x24 (32-bit) Version: 5 Unit Type: DW_UT_compile (1) Abbrev Offset: 0x0 Pointer Size: 8 <0>: Abbrev Number: 1 (DW_TAG_compile_unit) DW_AT_stmt_list : 0x0 <11> DW_AT_low_pc : 0x0 <19> DW_AT_high_pc : 5 <1a> DW_AT_name: tui-layout-asm-short-prog.S <1e> DW_AT_comp_dir: /home/vries/gdb_versions/devel <22> DW_AT_producer: GNU AS 2.37.50 <26> DW_AT_language: 32769(MIPS assembler) ... First we have: ... A DW_AT_comp_dir attribute whose value is a null-terminated string containing the current working directory of the compilation command that produced this compilation unit in whatever form makes sense for the host system. ... The DW_AT_comp_dir attribute looks correct, it matches pwd -P. Then we have: ... A DW_AT_name attribute whose value is a null-terminated string containing the full or relative path name (relative to the value of the DW_AT_comp_dir attribute, see below) of the primary source file from which the compilation unit was derived. ... That looks incorrect. It's a relative path name, so it's relative to /home/vries/gdb_versions/devel, which makes it /home/vries/gdb_versions/devel/tui-layout-asm-short-prog.S, which is a non-existent file. For comparison, we have with dwarf 4 instead: ... <19> DW_AT_name: /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.S <1d> DW_AT_comp_dir: /home/vries/gdb_versions/devel ... -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/28629] [gas, --gdwarf-5] File 0 has wrong dir
https://sourceware.org/bugzilla/show_bug.cgi?id=28629 --- Comment #1 from Tom de Vries --- Then let's look at the .debug_line section: ... $ readelf -wl tui-layout-asm-short-prog.o The Directory Table (offset 0x22, lines 2, columns 1): Entry Name 0 /home/vries/gdb_versions/devel 1 /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.tui The File Name Table (offset 0x30, lines 2, columns 2): Entry Dir Name 0 0 tui-layout-asm-short-prog.S 1 1 tui-layout-asm-short-prog.S ... It's the same problem. File 0 has dir 0, which spells out the non-existent /home/vries/gdb_versions/devel/tui-layout-asm-short-prog.S. For completeness, the comparison with dwarf 4 here as well: ... The Directory Table (offset 0x1c): 1 /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.tui The File Name Table (offset 0x56): Entry Dir TimeSizeName 1 1 0 0 tui-layout-asm-short-prog.S ... -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/28629] [gas, --gdwarf-5] File 0 has wrong dir
https://sourceware.org/bugzilla/show_bug.cgi?id=28629 --- Comment #2 from Tom de Vries --- Created attachment 13807 --> https://sourceware.org/bugzilla/attachment.cgi?id=13807&action=edit Tentative patch Using this patch we have instead: ... <1a> DW_AT_name: /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.S <1e> DW_AT_comp_dir: /home/vries/gdb_versions/devel ... and: ... The Directory Table (offset 0x22, lines 2, columns 1): Entry Name 0 /home/vries/gdb_versions/devel 1 /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.tui The File Name Table (offset 0x30, lines 2, columns 2): Entry Dir Name 0 1 tui-layout-asm-short-prog.S 1 1 tui-layout-asm-short-prog.S ... Both problems are fixed: - the DW_AT_name is now absolute with the correct prefix, - file 0 now has dir 1, making it identical to file 1. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/28629] [gas, --gdwarf-5] File 0 has wrong dir
https://sourceware.org/bugzilla/show_bug.cgi?id=28629 Tom de Vries changed: What|Removed |Added CC||nickc at sourceware dot org --- Comment #3 from Tom de Vries --- Patch submitted: https://sourceware.org/pipermail/binutils/2021-November/118654.html -- You are receiving this mail because: You are on the CC list for the bug.
