Which options does /debug:full conflict with?

[jirina]

I am trying to use VTune Amplifier and I am supposed to change the release configuration by using /debug:full in it. I found in the documentation that if a conflicting option is found on the command line, /debug:full is ignored. This is exactly what is happening in my case, so I would like to ask which if the following options is in a conflict with the full debug information:

/nologo /debug:full /MP /O2 /fpp /fixed /extend_source:132 /Qopenmp /fpscomp:general /warn:declarations /warn:unused /warn:truncated_source /warn:noalignments /assume:byterecl /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc100.pdb" /libs:static /threads /c

[Steven_L_Intel1]

Why do you think /debug:full is being ignored?  It isn't with those options, though /O2 is going to complicate debugging.

[jirina]

I checked the file size of the application program (.exe) and it changes in the Release Win32 configuration from 5082624 without the debug information to 5219328 bytes with full debug information. Would that little be typical when debug information is added? Also, when I use the version assumed to contain full debug information in VTune Amplifier I get the warning "Source/assembly code not available" (this is where my problems comes from - I am discussing it in Amplifier forum; I decided to discuss it also here to ask about compiler options).

[Steven_L_Intel1]

The size increase seems reasonable. You are getting infornation for routine symbols and line numbers, though the latter may not be very useful in an optimized program. 

[jirina]

I have just checked that the Debug Win32 configuration works well in VTune Amplifier and I get information about source code. So, it must be something in the release configuration what is a causing the problem in Amplifier. I will try resolving this issue in the corresponding forum; thank you for your comments and time.

[Steven_L_Intel1]

You probably also need to set the Linker option Debugging > Generate Debug Info.  I usually find it easier to just change the optimization level in a Debug configuration (and turn off run-time checking.)

[jirina]

Steve, thank you very much - enabling debug info in linker options was the key. I appreciate your prompt and patient help.