bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/27050] [2.36 Regression] ld -no-pie not recognized anymore


From: hjl.tools at gmail dot com
Subject: [Bug ld/27050] [2.36 Regression] ld -no-pie not recognized anymore
Date: Fri, 11 Dec 2020 13:18:48 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=27050

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
$ valgrind ./ld/ld-new -no-pie
==290969== Memcheck, a memory error detector
==290969== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==290969== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==290969== Command: ./ld/ld-new -no-pie
==290969== 
==290969== Conditional jump or move depends on uninitialised value(s)
==290969==    at 0x409A96: parse_args (lexsup.c:749)
==290969==    by 0x403DC6: main (ldmain.c:370)
==290969== 
./ld/ld-new: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)
==290969== 
==290969== HEAP SUMMARY:
==290969==     in use at exit: 21,161 bytes in 10 blocks
==290969==   total heap usage: 72 allocs, 62 frees, 43,232 bytes allocated
==290969== 
==290969== LEAK SUMMARY:
==290969==    definitely lost: 0 bytes in 0 blocks
==290969==    indirectly lost: 0 bytes in 0 blocks
==290969==      possibly lost: 0 bytes in 0 blocks
==290969==    still reachable: 21,161 bytes in 10 blocks
==290969==         suppressed: 0 bytes in 0 blocks
==290969== Rerun with --leak-check=full to see details of leaked memory
==290969== 
==290969== Use --track-origins=yes to see where uninitialised values come from
==290969== For lists of detected and suppressed errors, rerun with: -s
==290969== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]