-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack overflow #17
Comments
This looks like a KaTools problem indeed. Can you isolate the faulty commit on KaTools? |
Ok, so I've tested KaTools commit all the way to the is_agent_id fix, and I'm seeing the same error (just changing the line numbers). For prior KaTools commits, KaTie won't compile because the I then try to compile KaTie versions that predate this API change, but now the Dune / Opam configuration file is not finalized (e.g. missing a name, not making an building an executable, etc.), so now I'm skeptical that keeping rewinding KaTie's fixes to rewind KaTools' is the right way... From the error message, this stack overflow is coming from instantiation.ml, line 308, which from the GitBlame view, is not code that has been changed in 7 years. Upstream on the stack is line 260; again not changed in years. Upstream is 256; also not changed in years. And finally the stdlib's hashtb.find, which ... I doubt this is a bug in OCaml's stdlib. Rather, this looks like a problem resolving a concrete agent following a free operation, which sounds a lot like the side-effect & agent-id issues we've discovered this past month. Does sound like a good lead to you, or am I chasing the wrong goat here? |
Ok, I can have a look. Can you push a new test replicating the issue? Is there any issue with the other tests? |
Given the various branches and fixes in KaTools, I tried checking if the current state of KaTools/master (v4.1-97-gb9248b7) and KaTIE/master ("V0.3", pinned & fetched an hour ago) can read the traces I already have. Unfortunately, I get:
I believe the line about the overflow, got printed over the "nM events processed", hence the "overflowssed". Probably.
The testing simple query:
Is this an issue with KaTIE, or KaTools? I.e. should I iterate over KaTools commits until I find one that doesn't error..?
The text was updated successfully, but these errors were encountered: