I compile my progrs with debug info, but when I open a dissassembly window, it doesn't show the source code like it used to.
I don't what I forgot to do.
Andy
I guess you did something wrong.
In case you're not satisfied with this answer, I suggest to scrutinize how a question is to be asked intelligently - thus that those who are interested in replying don't have to make one-thousand guesses. :shock:
Verify your options for ml and link
ML:
/c /coff /Zi /Zd /nologo /Zp4
LINK:
/NOLOGO /DEBUG /debugtype:cv
and, um /SUBSYSTEM:somebody
LINK10 : fatal error LNK1221: a subsystem can't be inferred and must be defined
if it's a console app, /SUBSYSTEM:CONSOLE
if it's a windows app, /SUBSYSTEM:WINDOWS
the difference is one opens a console window, one does not
I just realized I left out that.
Now, link won't work because I have the wrong version.
I need this mspdl100.dll but link is saying that this version is wrong. 10.0.30319.1 which makes no sense.
My link version is 10.00.30319.01 built by: RTMRel
i think there is another issue...
using an older version of Link.exe might ensure a better match for symbol file format
I went back to version 6.14 and am using these.
Windbg can't unassemble my programs like it did at one time.
Maybe I need to try version 8.0 ?
ml /c /coff /Zi /Zd /nologo /Zp4 %1.asm
Link /SUBSYSTEM:WINDOWS /OPT:NOREF /NOLOGO /DEBUG %1.obj
if you add the /Zf switch to masm, it will make all symbols public
perhaps that's what you were used to, before
Quote
I need this mspdl100.dll but link is saying that this version is wrong
It seems you are using windbg with the masm32 package binaries.
Those binaries are very old,you need to use the c++ express binaries instead.
copy those binaries from the c++ (all the package ) to the masm32\bin and things must go better.