https://sourceware.org/bugzilla/show_bug.cgi?id=22426
--- Comment #2 from ky <yeokaiyeat at hotmail dot com> --- (In reply to ky from comment #0) > Created attachment 10584 [details] > testcase that crashes objcopy > > hello, during a fuzzing attempt on objcopy in binutils (2.26.1), fuzzed file > produces a crash when a certain fuzzed input is given. The same file is > tested again in binutils build 2.29.59.20171104 > > the error produced are as follows: > > ./objcopy: stYS7rQI : attempt to write out unknown reloc type > ./objcopy:stYS7rQI: Invalid operation > > =================================================================== > ==8555==ERROR: LeakSanitizer: detected memory leaks > > Direct leak of 9 byte(s) in 1 object(s) allocated from: > #0 0x7fdaf84d3602 in malloc > (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602 > #1 0xa755ec in xmalloc xmalloc.c:147 > > SUMMARY: AddressSanitizer: 9 byte(s) leaked in 1 allocation(s). > > attached is the test case UPDATE: Continued fuzzing on build 2.29.59.20171104 objcopy has found out another testcase that causes a memory exhaustion with the fuzzed input Output of console: ./objcopy: error: ./memexhaustion(.data) is too large (0xe8220008 bytes) ./objcopy:./memexhaustion[.data]: Memory exhausted -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
