On 21 juil, 07:31, Chris Ahn <[EMAIL PROTECTED]> wrote:
> [...]
>
> Yes. However, my problem is that IE automatically reports the error
> "stack overflow at line 0" (notice that it is at "line 0", which part
> of my code is at line 0? And it is not alerted using try-catch and
> alert(), purely automatically pops out. Also, it is showed in English,
> not in my local language like above.). Moreover, it is strange that it
> happens only sometimes, though most of the time it is ok. I have no
> means to know which time the error will occur and to debug a program
> which often executes properly. Aonther point is that when my program
> was very small, the error had never occurred, but when it growed into
> a considerable large scale, the error came sometimes. It is so
> boresome that I can only ascribe it to IE's bugs since in Firefox it
> never happens.
>
> That is the reason why I suspect function stack has relationship with
> my problem and wish setTimeout can solve it. It seems going off our
> topic. Lastly, if anybody could please provide any suggestion for my
> problem, I will be very grateful. Thanks anyway!

I'm not sure if this will help, but have you tried window.onerror ?
(http://developer.mozilla.org/en/docs/DOM:window.onerror) The "line 0"
could be because of many reasons... one I can think of is the use of
eval() to execute some scripts.

Sorry if I can't be much more of assistance in this issue, but when
something odd happens in my code, I usually walk step by step, butting
try...catch at some key points. It's a long process, but if your
program is structured, you'll be able to find the problem quick
enough.

Anyway. Good luck !


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to