On Mon, 26 Apr 2004 12:40:08 +0200, Ron Blaschke wrote:
> On Mon, 26 Apr 2004 11:48:22 +0200, Leopold Toetsch wrote:
>>> After, so I already got the interpreter.str file. I guess VC gets confused
>>> with the _CONST_STRING(i, __LINE__) thingy, where __LINE__ doesn't get
>>> expanded, and the whole results in _CONST_STRING_ instead of
>>> _CONST_STRING_1309, etc.
[snippy]
>> Yep, it should look like that. It's of course strange that during normal
>> compile this seems not be expanded like with /E.
[snappy]
Finally hunted down the little bugger: It's the -ZI flag, which enables the
Edit and Continue feature (which may, or may not, do some nasty things to
the code, to allow on-the-fly changes of a running program). The -Zi
("...program database (PDB) that contains type information and symbolic
debugging information for use with the debugger.") is ok, though.
config/init/hints/mswin32.pl
#Use Edit and Continue debugging if available
cc_debug => ($cc_output =~ m{/ZI} ? '-ZI' : '-Zi'),
Does anyone need the Edit and Continue feature? If not, above could simply
be changed to
cc_debug => '-Zi',
Ron
