bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/14207] New: x86_64 linker can produce a NULL GNU_RELRO segment


From: nickc at redhat dot com
Subject: [Bug ld/14207] New: x86_64 linker can produce a NULL GNU_RELRO segment
Date: Thu, 07 Jun 2012 16:02:50 +0000

http://sourceware.org/bugzilla/show_bug.cgi?id=14207

             Bug #: 14207
           Summary: x86_64 linker can produce a NULL GNU_RELRO segment
           Product: binutils
           Version: 2.23 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
        AssignedTo: address@hidden
        ReportedBy: address@hidden
    Classification: Unclassified


Created attachment 6438
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6438
Test source file

Using the uploaded relro.s source file, try the following using an
x86_64-pc-linux-gnu linker:

  % as relro.s -o relro.o
  % ld -z relro -z now -shared relro.o
  % readelf -l a.out
  [snip]
 Program Headers:
  Type           Offset             VirtAddr           PhysAddr
                 FileSiz            MemSiz              Flags  Align
  LOAD           0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x00000000000001e0 0x00000000000001e0  R      200000
  LOAD           0x0000000000000b88 0x0000000000200b88 0x0000000000200b88
                 0x0000000000000470 0x0000000000000cb8  RW     200000
  DYNAMIC        0x0000000000000bd0 0x0000000000200bd0 0x0000000000200bd0
                 0x0000000000000180 0x0000000000000180  RW     8
  NULL           0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x0000000000000000 0x0000000000000000         0
  [snip]

Note how the GNU_RELRO segment has been replaced by an empty segment, and that
no error or warning message was produced.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- 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]