-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Stack_overflow exception #410
Comments
Common culprit is that tail call is not optimized in general. You may face the same issue as #357 You can use You should be able to print to callstack with the following
|
OK, then that's a real problem. Our program relies on a parser combinator libraries with many self-recursive functions. Is there a deep technical reason for js_of_ocaml not to optimize tail calls? Would it be difficult to patch it? |
I also have the same problem and the same questions.! :) It would be nice to hear about the possibly technical reasons why tail calls are not optimised? (Also, I am a bit confused by the latter. I have zero knowledge about the zinc machine, but I would have expected the tail optimisation to occur before the generation of byte-code. Can anyone comment on this?) |
If I understand correctly, the file
|
We are having trouble with a Stack_overflow exception that we cannot trace... There is no
problem with the OCaml version and the stack size is reasonable. Other than polymorphic hash and equality function, are there other possible cause for such an error? Is there support for debuging of some kind in js_of_ocaml? For instance, is there a way to print a backtrace?
The text was updated successfully, but these errors were encountered: