Micha Nelissen schrieb:
Florian Klaempfl wrote:
Further, it allows an additional symbol to be given
procedure p;synchronized mycriticialsection;
Any suggestions about doing it better?
How to avoid deadlocks?
Indeed, I'am open to any suggestions :) Just an idea: maybe a global
call tree analysis with a call tree attributed with critical section
information can find potential deadlocks?
If a synchronized class is calling another
synchronized class ... :-S.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
