import std.string causes Optlink 'Error 32: Data Outside Segment Bounds : _DATA'

[Geod24]

Transferred from: https://issues.dlang.org/show_bug.cgi?id=8606

User @erisco reported (2012-09-01 15:22:37 CEST):

Unfortunately, I haven't narrowed the problem down. Here are the DirectX bindings that I am using that reproduce the error:
http://www.dsource.org/projects/bindings/browser/branches/erisco_directx/d?rev=401
(also included in the attachment)

Particularly, the import std.string in d3d11.d seems to be causing the error (when removed, no error).

To reproduce: build these DirectX bindings into a lib (the DirectX bindings depend on part of win32 ... working project and build attached). Then, write any program that imports windows.directx.d3d11 and compile it (of course, linking to the lib). Optlink will crash with this output:

OPTLINK (R) for Win32  Release 8.00.12
Copyright (C) Digital Mars 1989-2010  All rights reserved.
http://www.digitalmars.com/ctg/optlink.html

dxgi.lib
 Warning 2: File Not Found dxgi.lib
d3d11.lib
 Warning 2: File Not Found d3d11.lib
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA
..\lib\dmd_win32_x32.lib(d3d11) 
 Error 32: Data Outside Segment Bounds : _DATA

Sorry that this test case is so large; it may be useless, but I felt it was better to report it than do nothing.

User @erisco responded (2012-09-01 15:25:51 CEST):

Attachment was too large, so I uploaded it here

User @NeilBryant responded (2012-11-09 14:19:36 CET):

I was just having pretty much the exact same issue with 2.059.

I fixed it by deleting %temp%.rdmd