[Nasm-bugs] [Bug 3392650] New: Microsoft linker reports corrupt debug information
noreply-nasm at dev.nasm.us
noreply-nasm at dev.nasm.us
Wed Feb 19 08:26:42 PST 2020
https://bugzilla.nasm.us/show_bug.cgi?id=3392650
Bug ID: 3392650
Summary: Microsoft linker reports corrupt debug information
Product: NASM
Version: unspecified
Hardware: PC
OS: Windows
Status: OPEN
Severity: normal
Priority: Medium
Component: Assembler
Assignee: nobody at nasm.us
Reporter: michael at mehlich.com
CC: chang.seok.bae at intel.com, gorcunov at gmail.com,
hpa at zytor.com, nasm-bugs at nasm.us
Obtained from: Binary from nasm.us
Steps to reproduce:
create test file with script below
compile with nasm creating cv8 format debug
link with microsoft linker creating .pdb file
#this file: <mytest.pl>
#Versions used:
# nasm.exe: NASM version 2.14.02 compiled on Dec 26 2018
# link.exe: Microsoft (R) Incremental Linker Version 14.16.27035.0
#Commands:
# perl mytest.pl
# nasm -fwin64 mytest.asm -g -F cv8
# link.exe /nologo /incremental:no /subsystem:console mytest.obj /entry:main
/stack:65536,65536 /debug /pdb:mytest.pdb
#Error message from link step:
# mytest.obj : warning LNK4209: debugging information corrupt; recompile
module; linking object as if no debug info
# mytest.obj : warning LNK4209: debugging information corrupt; recompile
module; linking object as if no debug info
#program <mytest.asm> generated by following perl script:
open(OUTPUT,">mytest.asm");
print OUTPUT "\tglobal main\n";
print OUTPUT "segment .code\n";
print OUTPUT "main:\n";
for ($i=0; $i<10000; $i++) {
print OUTPUT "\tmov [rel .LC".$i."], rax\n";
}
print OUTPUT "\tret\n";
print OUTPUT "segment .rdata\n";
for ($i=0; $i<10000; $i++) {
print OUTPUT "\talignb 16, db 0\n";
print OUTPUT "\tglobal .LC".$i."\n";
print OUTPUT ".LC".$i.": dq 1\n";
}
close(OUTPUT);
--
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.
More information about the Nasm-bugs
mailing list