incubator-flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kessler CTR Mark J" <>
Subject RE: Running mxmlc in debug mode
Date Thu, 15 Nov 2012 12:02:04 GMT
Oh ok. Well if you want to keep it simple from the mxmlc, I would recommend simple traces inserted
into the problem area.  You can check the log on what it returns.
Using trace:

But before you use the trace feature, make sure you have not only the debug version of flash
player, but also have the TraceOutputFileEnable=1 in your mm.cfg file.

-----Original Message-----
From: João Fernandes [] 
Sent: Thursday, November 15, 2012 6:51
Subject: Re: Running mxmlc in debug mode

I don't mean building a debug version of my swf but be able to debug mxmlc
code so I can check where and why mxmlc is failing.

On 15 November 2012 11:47, Kessler CTR Mark J <>wrote:

> Well adding "-debug=true" for the command line options enables it to
> output more debug information including filenames with line numbers.
> -Mark
> -----Original Message-----
> From: João Fernandes []
> Sent: Thursday, November 15, 2012 6:32
> To:
> Subject: Running mxmlc in debug mode
> Does anyone know an easy way to run mxmlc in debug mode so I can check why
> it's reporting an weird error?
> I'm getting this kind of error
> SomeMXMLComponent.mxml(-1):  Error: Implicit coercion of a value of type
> SomeMXMLComponent to an unrelated type Object.
>     [mxmlc] <?xml version="1.0" encoding="utf-8"?>
> the weird part is it reports line -1 and error impliciting something to
> Object.
> --
> João Fernandes


João Fernandes

View raw message