Is it possible to monkey-patch trace() to substitute your own version, and set a breakpoint in it?
- Gordon -----Original Message----- From: Michael Montoya [mailto:[email protected]] Sent: Wednesday, January 23, 2013 4:02 AM To: [email protected] Subject: Re: AW: tracking down where "[trace] null" statements are comming from? Hey Chris, This may be a long shot, but how about using a an swf decompiler? I remember ising Trillix awhile back and was very impressed by the amount of detail provided in the diagnostics - It may pinpoint the source of your trace statement... Cheers! On Jan 23, 2013, at 11:46 AM, "[email protected]" <[email protected]> wrote: > Hi Omar, > > thanks for that input ... I knew that "trace" is a Flash function. I > was simply hoping for some guru here to give me a hint to the > "ultimate way to debug this" ;-) As it would help quite a lot ... > especially when having AMF serialization/deserialization problems (The > other type of problems that seem to be really hard to debug) > > Chris > > -----Ursprüngliche Nachricht----- > Von: Omar Gonzalez [mailto:[email protected]] > Gesendet: Mittwoch, 23. Januar 2013 11:00 > An: [email protected] > Betreff: Re: tracking down where "[trace] null" statements are comming from? > > On Wednesday, January 23, 2013, [email protected] wrote: > >> Unfortunately I can't set a breakpoint to the "trace" function ... >> perhaps it would be good if in future versions of flex there would be >> the means to somehow do this. >> >> Chris > > The trace() function is not a method from Flex it comes from Flash player. > There really isn't anything that can be done at the Flex level. > > I would try to get source code for your 3rd party libraries and search for > trace statements. If the source isn't available then you're probably out of > luck. Or you can try a decompiler. > > Also, I don't know enough about Adobe Scout but maybe that could help you > narrow it down. > > -omar
