You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 0632eb656a

accumulation

accumulation-v4.7

automata-finite

master

tud-infrastructure-2018-10-12

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '0632eb656a'

${ noResults }

prism-accumulation/prism-examples/phil

History

Joachim Klein 0632eb656a PrismCL: Catch unhandled Exceptions instead of delegating to default Java handling We are now catching unhandled Exceptions and errorAndExit. Previously, we relied on the Java handling, which would print the stack trace and kill the main thread. However, it seems that in the presence of thread pools (e.g., with the JAS library used by param/exact model checking), an unhandled exception would kill the main thread but not terminate PRISM. This could be triggered e.g. with prism prism-examples/dice/dice.pm -pf 'P>0.5[ F s=7 ]' -exact which generates an unhandled ClassCastException and previously would make PRISM hang indefinitely. git-svn-id: https://www.prismmodelchecker.org/svn/prism/prism/trunk@11537 bbc10eb1-c90d-0410-af57-cb519fbb1720		10 years ago
..
nofair	Example fixes re new semantics (result reported for initial state by default) - need more filters.	15 years ago
original	PrismCL: Catch unhandled Exceptions instead of delegating to default Java handling	10 years ago