Bug 4324 – Optlink silently ignores corrupt object file

Status
RESOLVED
Resolution
WORKSFORME
Severity
regression
Priority
P2
Component
tools
Product
D
Version
D2
Platform
x86
OS
Windows
Creation time
2010-06-15T12:30:00Z
Last change time
2017-01-10T01:41:16Z
Keywords
Optlink
Assigned to
nobody
Creator
torhu

Attachments

IDFilenameSummaryContent-TypeSize
663test.objSample corrupt object fileapplication/octet-stream517

Comments

Comment #0 by torhu — 2010-06-15T12:30:09Z
Created attachment 663 Sample corrupt object file This code compiled with DMD 1.062 results in a corrupt object file: --- void main() { char[] a; const b = ""; a ~= b; } --- Optlink 8.00.1 prints this error handed that file: OPTLINK (R) for Win32 Release 8.00.1 Copyright (C) Digital Mars 1989-2004 All rights reserved. test.obj(test) Offset 0018FH Record Type 009D Error 16: Index Range --- errorlevel 1 Optlink 8.00.2 prints nothing, but doesn't produces an exe either.
Comment #1 by torhu — 2010-06-15T12:37:26Z
Sorry, it's DMD 1.061.
Comment #2 by nfxjfg — 2010-06-15T16:50:12Z
Why did you report this twice? See bug 4315.
Comment #3 by bus_dbugzilla — 2011-05-29T15:04:39Z
They're two separate issues. That other issue, #4315, is about DMD creating a corrupt object file. But this one is about Optlink mishandling that corrupt object file.
Comment #4 by bugzilla — 2012-01-31T21:31:28Z
Linking with later optlink gives: link test.obj; OPTLINK (R) for Win32 Release 8.00.12 Copyright (C) Digital Mars 1989-2010 All rights reserved. http://www.digitalmars.com/ctg/optlink.html test.obj(test) Offset 0018FH Record Type 009D Error 16: Index Range