I have an application that compiles & runs just fine as long as /dbglibs is specified at compile-time. It works fine with:
/dbglibs /debug:full /pdbfile
as well as with
/dbglibs /optimize:5
but if I try /nodbglibs with either of them, I get an access violation.
For the same program, if I specify /unroll:n where n>0, the program will crash unless /check:bounds is also called.
So are these interactions reasonable to those more learned? I've found workarounds, so its not a big deal; but is seems quite odd.
Matt.
Compilation options & crashes.
Per informazioni complete sulle ottimizzazioni del compilatore, consultare l'Avviso sull'ottimizzazione

