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
==== 1.par error: No output from nuxmv ====
java.lang.Exception: No output from nuxmv
at uuverifiers.catra.NUXMVInstance.<init>(NUXMVBackend.scala:255)
at uuverifiers.catra.NUXMVBackend.solveSatisfy(NUXMVBackend.scala:23)
at uuverifiers.catra.SolveRegisterAutomata$.runInstance(SolveRegisterAutomata.scala:93)
at uuverifiers.catra.SolveRegisterAutomata$.$anonfun$runInstances$3(SolveRegisterAutomata.scala:109)
at uuverifiers.catra.SolveRegisterAutomata$.$anonfun$runInstances$1(SolveRegisterAutomata.scala:53)
at uuverifiers.catra.SolveRegisterAutomata$.$anonfun$runInstances$1$adapted(SolveRegisterAutomata.scala:98)
at scala.collection.immutable.List.foreach(List.scala:333)
at uuverifiers.catra.SolveRegisterAutomata$.runInstances(SolveRegisterAutomata.scala:98)
at uuverifiers.catra.SolveRegisterAutomata$.delayedEndpoint$uuverifiers$catra$SolveRegisterAutomata$1(SolveRegisterAutomata.scala:124)
at uuverifiers.catra.SolveRegisterAutomata$delayedInit$body.apply(SolveRegisterAutomata.scala:48)
at scala.Function0.apply$mcV$sp(Function0.scala:39)
at scala.Function0.apply$mcV$sp$(Function0.scala:39)
at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:17)
at scala.App.$anonfun$main$1(App.scala:76)
at scala.App.$anonfun$main$1$adapted(App.scala:76)
at scala.collection.IterableOnceOps.foreach(IterableOnce.scala:563)
at scala.collection.IterableOnceOps.foreach$(IterableOnce.scala:561)
at scala.collection.AbstractIterable.foreach(Iterable.scala:926)
at scala.App.main(App.scala:76)
at scala.App.main$(App.scala:74)
at uuverifiers.catra.SolveRegisterAutomata$.main(SolveRegisterAutomata.scala:48)
at uuverifiers.catra.SolveRegisterAutomata.main(SolveRegisterAutomata.scala)
The text was updated successfully, but these errors were encountered:
I found the bug! The same counter, len1, is declared twice. This situation isn't discovered by the very rudimentary input validation, and apparently leads to an invalid nuxmv encoding. A future version will address this bug.
amandasystems
changed the title
crash when use nuxmv as backend to solve some instance
An invalid input the same counter is declared more than once is accepted
Mar 29, 2023
amandasystems
changed the title
An invalid input the same counter is declared more than once is accepted
An invalid input where the same counter is declared more than once is accepted
Mar 29, 2023
I have added validation to address the issue now; I feel like the best approach is to reject input where the same counter is declared more than once since it suggests a mistake.
Commmand is:
The contants of
1.par
are:The output on the terminal is"
The text was updated successfully, but these errors were encountered: