You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the axiom profiler with Mono, loading any log file of nontrivial size (more than a few megabytes) seems to cause a crash. Using Mono is currently the only way to run the axiom profiler on non-Windows OSs, so this issue might affect many users that want to try the profiler.
Probably related to this, the wiki of FStar reports the following:
Using mono, the profiler seems too slow to process any trace of nontrivial size (with a 15 Mo z3.log, it ran for an hour before I kill it);
The text was updated successfully, but these errors were encountered:
We (the VerCors developers) run into this frequently. Especially since our files are often several hundred megabytes. Even cutting log files down to 2mb, axiom profiler still seems to have problems.
The crash I am currently getting is that axiom profiler spends some time loading a file, then suddenly closes and prints "Eliminated" (in dutch) in my terminal. I will probably soon try analyzing this file on windows, to see if the problem is with axiom profiler or this specific log file.
EDIT: Our experiences are probably because of issue #35, as I get the exact same behaviour with my log files on linux as the behaviour described in that issue.
When running the axiom profiler with Mono, loading any log file of nontrivial size (more than a few megabytes) seems to cause a crash. Using Mono is currently the only way to run the axiom profiler on non-Windows OSs, so this issue might affect many users that want to try the profiler.
Probably related to this, the wiki of FStar reports the following:
The text was updated successfully, but these errors were encountered: