[Bug gprofng/30602] [2.41] gprofng test hangs on i686-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=30602 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Vladimir Mezentsev : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9d9f26d8b1a15561af02370f15be0af0d56ac5fa commit 9d9f26d8b1a15561af02370f15be0af0d56ac5fa Author: Vladimir Mezentsev Date: Wed Jul 12 15:03:28 2023 -0700 gprofng: 30602 [2.41] gprofng test hangs on i686-linux-gnu There were several problems in the gprofng testing: - we did not catch a timeout for each test. - we used exit() to stop a failed test. But this stops all other tests. - we used a time_t (long) type in smalltest.c instead of a long long type. PR gprofng/30602 * configure.ac: Launch only native testing. * configure: Rebuild. * testsuite/config/default.exp: Set TEST_TIMEOUT. * testsuite/gprofng.display/setpath_map.exp: Use return instead of exit. * testsuite/gprofng.display/gp-archive.exp: Likewise. * testsuite/gprofng.display/gp-collect-app_F.exp: Likewise. * testsuite/gprofng.display/display.exp: Delete an unnecessary test for native testing. * testsuite/lib/display-lib.exp (run_native_host_cmd): Add timeout. * testsuite/lib/smalltest.c: Use a long long type instead of time_t. -- You are receiving this mail because: You are on the CC list for the bug.
Issue 60532 in oss-fuzz: binutils:fuzz_dwarf: Use-of-uninitialized-value in offset_from_vma
Updates: Labels: -restrict-view-commit Comment #3 on issue 60532 by sheriffbot: binutils:fuzz_dwarf: Use-of-uninitialized-value in offset_from_vma https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60532#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 57997 in oss-fuzz: binutils:fuzz_as: Stack-overflow in i386_intel_simplify
Updates: Labels: -restrict-view-commit -deadline-approaching Deadline-Exceeded Comment #3 on issue 57997 by sheriffbot: binutils:fuzz_as: Stack-overflow in i386_intel_simplify https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57997#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/30632] ld segfaults if linker script includes a STARTUP line.
https://sourceware.org/bugzilla/show_bug.cgi?id=30632 --- Comment #2 from Peter Chubb --- Created attachment 14962 --> https://sourceware.org/bugzilla/attachment.cgi?id=14962=edit Possible fix -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30632] ld segfaults if linker script includes a STARTUP line.
https://sourceware.org/bugzilla/show_bug.cgi?id=30632 --- Comment #1 from Peter Chubb --- Created attachment 14961 --> https://sourceware.org/bugzilla/attachment.cgi?id=14961=edit script that causes segfault Do: ld -T script.ld and watch the segmentation violation. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30632] ld segfaults if linker script includes a STARTUP line.
https://sourceware.org/bugzilla/show_bug.cgi?id=30632 Peter Chubb changed: What|Removed |Added Summary|ld segfaults if linker |ld segfaults if linker |script includes |script includes a STARTUP ||line. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30632] New: ld segfaults if linker script includes
https://sourceware.org/bugzilla/show_bug.cgi?id=30632 Bug ID: 30632 Summary: ld segfaults if linker script includes Product: binutils Version: 2.42 (HEAD) Status: UNCONFIRMED Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: peter.chubb at unsw dot edu.au Target Milestone: --- ld -Tscript.ld segfaults in ldlang.c when a startup file is given in the script. The problem is commit fb221fba1a5eb05355f248d6aa1e3ab4316899fd which makes first_file NULL if NULL is My script.ld contains: STARTUP(crt0.o); backtrace: #0 lang_startup (name=0x556f50a0 "crt0.o") at ../../ld/ldlang.c:8704 #1 0x55564e7a in yyparse () at ../../ld/ldgram.y:850 #2 0x55569e88 in parse_args (argc=, argv=) at ../../ld/lexsup.c:1385 #3 0x555634f5 in main (argc=, argv=) at ../../ld/ldmain.c:375 (gdb) print first_file $1 = (lang_input_statement_type *) 0x0 first_file is set in lang_init at line 1331 of ld/ldlang.c: first_file = lang_add_input_file (NULL, lang_input_file_is_marker_enum, NULL); lang_add_input_file() passes its first argument (here NULL) to new_afile() Commit fb221fba1a5eb05355f248d6aa1e3ab4316899fd changed new_afile() to return NULL if the name was NULL. (near line 1139 of ldlang.c): name = ldfile_possibly_remap_input (name); if (name == NULL) return NULL; I suggest the check for NULL here is incorrect, as NULL is an allowed value for the name. Commenting out the if statement and its return fixes the issue. -- You are receiving this mail because: You are on the CC list for the bug.
