trace() output stops working with -optimize=true

I guess this one could be filed under the 'guess that makes sense' category, but none the less was a bit of a head-scratcher to figure out.

Basically, I have a couple of external libraries which I'm using in my current Flex project. I was trying to use the global trace() function within these libraries, but there was nothing getting output. Wha? I was in debug mode... I have the debug player... this has worked before... wtf?

Skip back... about a month ago my Subversion provider did a major migration which caused me massive headaches, and basically, I had to wipe out all my projects, and check them out fresh from the new svn repository locations, instead of just updating the repo address. In doing this, I thought I got all my settings correct, but alas...

One particular Library project (the project in question above) had -optimize=true as compiler argument. I saw this and didn't figure it for the issue as you have the -debug argument, and -debug-verbose which deal with output stuff.

Finally, after googling/flexcodering/blog searching/etc... along with confirming my mm.cfg file and flashlog.txt setup was correct, I began trying stuff willy-nilly to get this fixed. That's when I discovered that -optimize=true does indeed prevent any trace outputs.

And that's the morale of this blog post :-)