I would say the "undefined" trace matches a simple "trace(one_var);" in a
file which is particular to your offline project (not in shared libs).
To talk again about events based stack overflow, I would put two surrounding
"trace" in event handlers to see stacked functions :
> function handlerFunction(e:event):void {
> trace('handlerFunction for', e.type);
> // code goes here
> trace('/handlerFunction for',e.type);
> }
thomas
---
http://www.web-attitude.fr/
msn : [email protected]
softphone : sip:[email protected] <sip%[email protected]>
téléphone portable : +33601 822 056
2009/7/8 Erik de Bruin <[email protected]>
>
>
> Hi,
>
> Thanks for your swift reply.
>
> I did a check to see if what you suggest might be the case, by
> inserting a trace() in all the event dispatch and handler functions,
> but nowhere in the chain does this type of recursion occur.
>
> I do however see that the entire chain is run dozens of times, while
> the data structure is build from the data in the database. But this is
> expected behavior, and the case remains that this code functions
> flawlessly in the online version (again, build from the same
> codebase).
>
> Any suggestions on how to proceed with debugging, as well as why the
> stack trace shows a single final line with only the word "undefined"
> in it, are much apreciated.
>
> Regards,
>
> EdB
>
>
> On Wed, Jul 8, 2009 at 5:44 PM, thomas
> parquier<[email protected] <mailinglists%40web-attitude.fr>>
> wrote:
> >
> >
> > You may have one type of event (A) handled in a function which dispatches
> > another type of event (B) handled in a function which dispatches an event
> of
> > type A. If dispatching occurs before handler functions return you may get
> a
> > stack overflow.
> >
> > thomas
> > ---
> > http://www.web-attitude.fr/
>
> > msn : [email protected]<thomas.parquier%40web-attitude.fr>
> > softphone : sip:[email protected] <webattitude%40ekiga.net>
> > téléphone portable : +33601 822 056
> >
> >
> > 2009/7/8 erikdebruin_nl
> > <[email protected]<erikdebruin%2Bflexcoders%40gmail.com>
> >
> >>
> >>
> >> Hi,
> >>
> >> I've Googled me senseless, but I can't find a clue to my latest problem:
> >>
> >> When I run my application in the browser, all is fine. When the same app
> >> in AIR (we've build it so the same codebase is shared between on- and
> >> offline versions), I get an exception and the last line in the stack
> trace
> >> (as shown in the Console) reads "undefined". The error dialog the player
> >> throws up (after clicking on the "Resume (F8)" button in the debug
> >> perspective) tells me a "stack overflow" happened.
> >>
> >> The "funny" thing is, when I disable the code that seems to be the cause
> >> (taking my clues from the stack trace), the problem remains, but the
> stack
> >> trace tells me another line is the problem... and so on and on.
> >>
> >> Google tells me that a stack overflow mostly has to do with rampant
> >> recursion, but my app doesn't use recursion anywhere. It does however
> use a
> >> lot of event chains. Do these count as "recursion"?
> >>
> >> What does it mean that the last line of the stack trace reads
> "undefined"?
> >>
> >> Any suggestions about further debugging my problem are very welcome!
> >>
> >> Thanks in advance,
> >>
> >> EdB
> >>
> >
> >
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
>
