[Bug ld/10957] Missing option to really print section+offset
https://sourceware.org/bugzilla/show_bug.cgi?id=10957 Alan Modra changed: What|Removed |Added Target Milestone|--- |2.41 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/30653] New: segment fault in as
https://sourceware.org/bugzilla/show_bug.cgi?id=30653 Bug ID: 30653 Summary: segment fault in as Product: binutils Version: 2.39 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: mengda2020 at iscas dot ac.cn Target Milestone: --- Created attachment 14986 --> https://sourceware.org/bugzilla/attachment.cgi?id=14986&action=edit POC as segment fault Hello, Binutils developers! I found a segment fault in as. It caused the operand function to keep recursing at line 1049 in expr.c, exhausting the stack resources Please confirm. Thanks! Test Environment Ubuntu 20.04, 64 bit binutils (version: v2.39 How to trigger Compile the program Run command $ ./as --alternate --gdwarf-5 --gstabs --gstabs+ --traditional-format -a -g $POC Details ''' GDB report $.(gdb) set args --alternate --gdwarf-5 --gstabs --gstabs+ --traditional-format -a -g $POC out/default/crashes/id\:01\,sig\:11\,src\:001595+001814\,time\:73187270\,execs\:7351020\,op\:splice\,rep\:4 (gdb) r Starting program: /home/cmd/sp/Fuzz/aflpp_fuzz/OSmart/Binutils/as/al_alternate_gdwarf-5_gstabs_gstabs+_traditional-format_a_g/as_2/as --alternate --gdwarf-5 --gstabs --gstabs+ --traditional-format -a -g out/default/crashes/id\:01\,sig\:11\,src\:001595+001814\,time\:73187270\,execs\:7351020\,op\:splice\,rep\:4 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4: Assembler messages: out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4: Warning: end of file not at end of a line; newline inserted out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4:3: Error: unknown pseudo-op: `.�' out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4:3: Error: unknown pseudo-op: `.' out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4:3: Error: invalid character (0x80) in mnemonic out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4:4: Error: junk at end of line, first unrecognized character valued 0x12 out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4:4: Error: junk at end of line, first unrecognized character valued 0x4 out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4:4: Error: bad expression out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4:4: Error: bad expression Program received signal SIGSEGV, Segmentation fault. ''' backtrace: ''' #3584 0x00526334 in operand (expressionP=0x7fffc900, mode=expr_normal) at expr.c:1049 #3585 0x00526334 in operand (expressionP=0x7fffc900, mode=expr_normal) at expr.c:1049 #3586 0x0051efac in expr (rankarg=5, resultP=0x7fffc900, mode=expr_normal) at expr.c:1800 #3587 0x0051f24d in expr (rankarg=0, resultP=0x7fffd180, mode=expr_normal) at expr.c:1814 #3588 0x00591b2d in get_segmented_expression (expP=0x7fffd180) at read.c:5616 #3589 0x0057afa6 in get_known_segmented_expression (expP=0x7fffd180) at read.c:5632 #3590 0x0057d083 in assign_symbol (name=0x6310084e ".", mode=0) at read.c:3126 #3591 0x0056a977 in equals (sym_name=0x6310084e ".", reassign=1) at read.c:5753 #3592 0x00567720 in read_a_source_file ( name=0x7fffe2db "out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4") at read.c:1075 #3593 0x004dc118 in perform_an_assembly_pass (argc=0, argv=0x60700108) at as.c:1256 #3594 0x004d6d05 in main (argc=2, argv=0x60700100) at as.c:1418 ''' -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/30654] New: segment fault in as at line 1520 in symbols.c
https://sourceware.org/bugzilla/show_bug.cgi?id=30654 Bug ID: 30654 Summary: segment fault in as at line 1520 in symbols.c Product: binutils Version: 2.39 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: mengda2020 at iscas dot ac.cn Target Milestone: --- Created attachment 14987 --> https://sourceware.org/bugzilla/attachment.cgi?id=14987&action=edit POC file as segment fault at line 1520 in symbols.c Hello, Binutils developers! I found another segment fault in as. It caused the "resolve_symbol_value" function to keep recursing at line 1520 in symbols.c, exhausting the stack resources Please confirm. Thanks! Test Environment Ubuntu 20.04, 64 bit binutils (version: v2.39 How to trigger Compile the program Run command $ ./as --alternate --gdwarf-5 --gstabs --gstabs+ --traditional-format -a -g $POC Details ''' GDB report $.(gdb) set args --alternate --gdwarf-5 --gstabs --gstabs+ --traditional-format -a -g $POC (gdb) r ... out/default/crashes/id:00,sig:11,src:004216+003578,time:70426992,execs:7097863,op:splice,rep:2:3: Error: found ' ', expected: ')' out/default/crashes/id:00,sig:11,src:004216+003578,time:70426992,execs:7097863,op:splice,rep:2:3: Error: bad or irreducible absolute expression out/default/crashes/id:00,sig:11,src:004216+003578,time:70426992,execs:7097863,op:splice,rep:2: Error: symbol definition loop encountered at `B' out/default/crashes/id:00,sig:11,src:004216+003578,time:70426992,execs:7097863,op:splice,rep:2:2: Error: invalid operands (*UND* and *GAS `expr' section* sections) for `-' Program received signal SIGSEGV, Segmentation fault. ''' backtrace: ''' #3584 0x00526334 in operand (expressionP=0x7fffc900, mode=expr_normal) at expr.c:1049 #3585 0x00526334 in operand (expressionP=0x7fffc900, mode=expr_normal) at expr.c:1049 #3586 0x0051efac in expr (rankarg=5, resultP=0x7fffc900, mode=expr_normal) at expr.c:1800 #3587 0x0051f24d in expr (rankarg=0, resultP=0x7fffd180, mode=expr_normal) at expr.c:1814 #3588 0x00591b2d in get_segmented_expression (expP=0x7fffd180) at read.c:5616 #3589 0x0057afa6 in get_known_segmented_expression (expP=0x7fffd180) at read.c:5632 #3590 0x0057d083 in assign_symbol (name=0x6310084e ".", mode=0) at read.c:3126 #3591 0x0056a977 in equals (sym_name=0x6310084e ".", reassign=1) at read.c:5753 #3592 0x00567720 in read_a_source_file ( name=0x7fffe2db "out/default/crashes/id:01,sig:11,src:001595+001814,time:73187270,execs:7351020,op:splice,rep:4") at read.c:1075 #3593 0x004dc118 in perform_an_assembly_pass (argc=0, argv=0x60700108) at as.c:1256 #3594 0x004d6d05 in main (argc=2, argv=0x60700100) at as.c:1418 ''' -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30578] libavcodec/x86/mathops.h:125: Error: operand type mismatch for ` shr'
https://sourceware.org/bugzilla/show_bug.cgi?id=30578 Matthias Klose changed: What|Removed |Added CC||doko at debian dot org, ||jbeulich at suse dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30655] New: patch introducing remap-inputs causes build failure in edk2
https://sourceware.org/bugzilla/show_bug.cgi?id=30655
Bug ID: 30655
Summary: patch introducing remap-inputs causes build failure in
edk2
Product: binutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: dannf at dannf dot org
Target Milestone: ---
Copying from: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041495
edk2 has begun to FTBFS w/ recent buildutils. Log follow below. I bisected the
failure to
upstream commit fb221fba1a5 ("Add --remap-inputs option to the BFD linker").
After reverting that commit, this failure goes away.
dannf@xps13:/tmp/edk2-2023.05$ "gcc" -o
/tmp/edk2-2023.05/Build/OvmfX64/RELEASE_GCC5/X64/MdeModulePkg/Universal/StatusCodeHandler/Pei/StatusCodeHandlerPei/DEBUG/StatusCodeHandlerPei.dll
-nostdlib -Wl,-n,-q,--gc-sections -z common-page-size=0x40
-Wl,--entry,_ModuleEntryPoint -u _ModuleEntryPoint
-Wl,-Map,/tmp/edk2-2023.05/Build/OvmfX64/RELEASE_GCC5/X64/MdeModulePkg/Universal/StatusCodeHandler/Pei/StatusCodeHandlerPei/DEBUG/StatusCodeHandlerPei.map,--whole-archive
-Wl,-melf_x86_64,--oformat=elf64-x86-64,-pie -flto -Os
-Wl,--start-group,@/tmp/edk2-2023.05/Build/OvmfX64/RELEASE_GCC5/X64/MdeModulePkg/Universal/StatusCodeHandler/Pei/StatusCodeHandlerPei/OUTPUT/static_library_files.lst,--end-group
-g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror
-Wno-array-bounds -include AutoGen.h -fno-common -ffunction-sections
-fdata-sections -fno-stack-protector
-DSTRING_ARRAY_NAME=StatusCodeHandlerPeiStrings -m64 -march=x86-64
-fno-stack-protector "-DEFIAPI=__attribute__((ms_abi))"
-maccumulate-outgoing-args -mno-red-zone -Wno-address -mcmodel=small -fpie
-fno-asynchronous-unwind-tables -Wno-address -fno-omit-frame-pointer -flto
-DUSING_LTO -Wno-unused-but-set-variable -Wno-unused-const-variable
-DMDEPKG_NDEBUG -mno-mmx -mno-sse -D DISABLE_NEW_DEPRECATED_INTERFACES -D
TDX_GUEST_SUPPORTED -D ENABLE_MD5_DEPRECATED_INTERFACES
-Wl,--defsym=PECOFF_HEADER_SIZE=0x228
-Wl,--script=/tmp/edk2-2023.05/BaseTools/Scripts/GccBase.lds -Wno-error
/usr/bin/ld: warning: IoFifoSev.obj: missing .note.GNU-stack section implies
executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future
version of the linker
/usr/bin/ld: warning: cannot find entry symbol _ModuleEntryPoint; defaulting to
0240
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 assertion fail
../../bfd/elflink.c:10611
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.40.90.20230714 asse
Issue 58411 in oss-fuzz: binutils:fuzz_as: Unexpected-exit in xexit
Updates: Labels: Deadline-Approaching Comment #2 on issue 58411 by sheriffbot: binutils:fuzz_as: Unexpected-exit in xexit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58411#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - 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 58205 in oss-fuzz: binutils:fuzz_objdump_safe: Direct-leak in xmalloc
Updates: Labels: -restrict-view-commit -deadline-approaching Deadline-Exceeded Comment #3 on issue 58205 by sheriffbot: binutils:fuzz_objdump_safe: Direct-leak in xmalloc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58205#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.
[Bug ld/30655] [2.41 Regression] patch introducing remap-inputs causes build failure in edk2
https://sourceware.org/bugzilla/show_bug.cgi?id=30655 Matthias Klose changed: What|Removed |Added Summary|patch introducing |[2.41 Regression] patch |remap-inputs causes build |introducing remap-inputs |failure in edk2 |causes build failure in ||edk2 CC||doko at debian dot org, ||nickc at sourceware dot org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30655] [2.41 Regression] patch introducing remap-inputs causes build failure in edk2
https://sourceware.org/bugzilla/show_bug.cgi?id=30655 --- Comment #1 from dann frazier --- fwiw, this seems to resolve the issue for me. It isn't clear from the context why this new feature introduced a return here. diff --git a/ld/ldlang.c b/ld/ldlang.c index 4b86c164843..d5a94d47e4b 100644 --- a/ld/ldlang.c +++ b/ld/ldlang.c @@ -1137,8 +1137,6 @@ new_afile (const char *name, lang_has_input_file = true; name = ldfile_possibly_remap_input (name); - if (name == NULL) -return NULL; p = new_stat (lang_input_statement, stat_ptr); memset (&p->the_bfd, 0, -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/30653] segment fault in as
https://sourceware.org/bugzilla/show_bug.cgi?id=30653 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from Alan Modra --- Running out of stack because a fuzzed input has an enormous expresion, is not a bug in gas. This sort of fuzzer input does not help improve the quality of gas in the real world. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/30654] segment fault in as at line 1520 in symbols.c
https://sourceware.org/bugzilla/show_bug.cgi?id=30654 Alan Modra changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Alan Modra --- As for pr30653. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30655] [2.41 Regression] patch introducing remap-inputs causes build failure in edk2
https://sourceware.org/bugzilla/show_bug.cgi?id=30655 --- Comment #2 from Alan Modra --- (In reply to dann frazier from comment #1) > fwiw, this seems to resolve the issue for me. It seems very likely then that the fix for pr30632, already applied mainline and 2.41 branch will fix this problem. Can you check, please? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30578] libavcodec/x86/mathops.h:125: Error: operand type mismatch for ` shr'
https://sourceware.org/bugzilla/show_bug.cgi?id=30578 Jan Beulich changed: What|Removed |Added Last reconfirmed||2023-07-20 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Jan Beulich --- See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108941. The cast in (uint8_t)(-s) isn't honored by gcc when s can be determined to be a plain number, making it emit a negative value. Negative shift counts of course make no sense (on x86 at least). See the description of the referenced binutils patch as to the resulting misbehavior for RCL and RCR. For SHL/SHR etc the behavior would still be correct, but (dis)allowing negative shift counts there is a matter of consistency. I won't mark this "invalid" right away, to allow for discussion to happen here that should have happened on the patch submission (if need be). -- You are receiving this mail because: You are on the CC list for the bug.
