bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/21884] [2.29/2.30 Regression] ld segfaulting building memtest86


From: matz at suse dot de
Subject: [Bug ld/21884] [2.29/2.30 Regression] ld segfaulting building memtest86
Date: Fri, 11 Aug 2017 13:42:08 +0000

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

Michael Matz <matz at suse dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |matz at suse dot de
         Resolution|FIXED                       |---

--- Comment #28 from Michael Matz <matz at suse dot de> ---
This still reproduces for me, on i586 and on x86_64.  I don't need to build
binutils in any special way, on my host x86_64, with gcc 4.7:

% git status
# On branch binutils-2_29-branch
...
nothing added to commit but untracked files present (use "git add" to track)
% mkdir dev && cd dev
% ../configure --disable-gdb
% make CFLAGS=-g -j8
...
% echo "" > foo
% cat memtest.lds
OUTPUT_FORMAT("elf32-i386");
OUTPUT_ARCH(i386);

ENTRY(_start); 
SECTIONS {
        . = 0x10000;
        _start = . ;
        .data : {
                *(.data)
        }
}
% ./ld/ld-new -T memtest.lds -b binary foo -o memtest

valgrind shows me this backtrace:

==3890== Invalid read of size 4
==3890==    at 0x49386B: _bfd_elf_create_got_section (elflink.c:158)
==3890==    by 0x4D3B62: elf_i386_link_setup_gnu_properties (elf32-i386.c:7025)
==3890==    by 0x42C393: gldelf_x86_64_after_open (eelf_x86_64.c:1169)
==3890==    by 0x42373C: ldemul_after_open (ldemul.c:64)
==3890==    by 0x418E3D: lang_process (ldlang.c:7093)
==3890==    by 0x41D1E5: main (ldmain.c:437)
==3890==  Address 0x28 is not stack'd, malloc'd or (recently) free'd

So yes, the elf_i386_link_setup_gnu_properties function is most definitely
called.

-- 
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]