bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/24035] New: wrong VMA when not specified explicitly


From: stsp at users dot sourceforge.net
Subject: [Bug ld/24035] New: wrong VMA when not specified explicitly
Date: Tue, 25 Dec 2018 21:05:10 +0000

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

            Bug ID: 24035
           Summary: wrong VMA when not specified explicitly
           Product: binutils
           Version: 2.31
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: stsp at users dot sourceforge.net
  Target Milestone: ---

Created attachment 11493
  --> https://sourceware.org/bugzilla/attachment.cgi?id=11493&action=edit
test case

Attached is a test-case.
Please run test.sh.
It will link multiple objects (of freedos)
and look for a symbol address in the linker map.
This symbol is in the section .ibss, which VMA
is not specified in the linker script. The value
that linker takes, looks completely wrong. It was
reported that older linker (from ubuntu xenial) do
work properly in this case, just using the VMA after
the previous section, which is in this case .idata.
But newer linker seems to use the VMA of the section
.itext.
I already fixed the linker script, but I think this
behaviour change is a regression.

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