[erlang-questions] erlang-questions Digest, Vol 12, Issue 102

[Ulf Wiger]

There are some fairly exciting tools that can help along
the way:

1 McErlang is an innovative way of model checking erlang code
2 gen_trace has facilities for exporting to model checkers,
  and some work has been done on analysing "abstract
  traces" from running systems
3 QuickCheck doesn't go for deadlocks per se, but has a
  tendency to find weird and wonderful bugs in any program.

[1] http://babel.ls.fi.upm.es/~fred/McErlang/
[2] http://www.cs.chalmers.se/~hanssv/erlang_tracing/abstrfun.html
     http://www.erlang.org/pipermail/erlang-questions/2002-February/004343.html
[3] http://www.quviq.com

BR,
Ulf W

2008/5/31 Raoul Duke <raould@REDACTED>:
> hi,
>
>> With respect to avoiding deadlocks or ensuring there are none, I would
>> design my system based on CSP (Communicating sequential processes)
>> concepts. i.e Independent processes communicating via a pipe without
>> any shared memory.
>
> I believe that's sort of what Erlang does by nature ;-) so it is then
> a question of what modeling tools exist and how well they work. It
> isn't enough to design with CSP, you can still create deadlocks in it
> - you have to run a checker over it to try to prove there isn't any.
>
> sincerely.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>