bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/22846] New: i686-w64-mingw32 cross linker generates truncated bi


From: despair at rvx86 dot net
Subject: [Bug ld/22846] New: i686-w64-mingw32 cross linker generates truncated binary image
Date: Thu, 15 Feb 2018 01:58:36 +0000

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

            Bug ID: 22846
           Summary: i686-w64-mingw32 cross linker generates truncated
                    binary image
           Product: binutils
           Version: 2.30
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: despair at rvx86 dot net
  Target Milestone: ---

Using the cross-linker with any set of object files results in the following
repeated message, emitting a truncated binary image that is corrupt:

DJ: zero vma section reloc detected: `.text' #0 f=283

Host:
address@hidden ~]$ uname -a
OpenBSD ntdev1.rvx86.net 6.2 GENERIC.MP#5 amd64

Target: i686-w64-mingw32 shared library (.dll)
Built binutils from straight from the tarball, nothing fancy.

Steps to reproduce:
1. Build binutils 2.30 for i686-w64-mingw32.
2. Build GCC or Clang for the same target.
3. Compile and link any shared library target, even the most minimal:

#include <windows.h>

BOOL FAR PASCAL DllMain( HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpReserved
)
{
        // Perform actions based on the reason for calling.
        switch( fdwReason )
        {
        case DLL_PROCESS_ATTACH:
                // Initialize once for each new process.
                // Return FALSE to fail DLL load.
                break;

        case DLL_THREAD_ATTACH:
                // Do thread-specific initialization.
                break;

        case DLL_THREAD_DETACH:
                // Do thread-specific cleanup.
                break;

        case DLL_PROCESS_DETACH:
                // Perform any necessary cleanup.
                break;
        }
        return TRUE;  // Successful DLL_PROCESS_ATTACH.
}

Attempting to link produces the above message.

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