• I correct an english mistake in my post, i wanted to write "broader", n

    From Wisdom90@21:1/5 to All on Mon Jan 13 18:10:32 2020

    Read this:

    I correct an english mistake in my post, i wanted to write "broader",
    not brother, read again:

    About modelizations and detection of race conditions and deadlocks in
    parallel programming..

    I have just taken further a look at the following project in Delphi
    called DelphiConcurrent by an engineer called Moualek Adlene from France:


    And i have just taken a look at the following webpage of Dr Dobb's journal:

    Detecting Deadlocks in C++ Using a Locks Monitor


    And i think that both of them are using technics that are not as good
    as analysing deadlocks with Petri Nets in parallel applications ,
    for example the above two methods are only addressing locks or mutexes
    or reader-writer locks , but they are not addressing semaphores
    or event objects and such other synchronization objects, so they
    are not good, this is why i have written a tutorial that shows my
    methodology of analysing and detecting deadlocks in parallel
    applications with Petri Nets, my methodology is more sophisticated
    because it is a generalization and it modelizes with Petri Nets the
    brother range of synchronization objects, and in my tutorial i will add
    soon other synchronization objects, you have to look at it, here it is:


    You have to get the powerful Tina software to run my Petri Net examples
    inside my tutorial, here is the powerful Tina software:


    Also to detect race conditions in parallel programming you have to take
    a look at the following new tutorial that uses the powerful Spin tool:


    This is how you will get much more professional at detecting deadlocks
    and race conditions in parallel programming.

    Thank you,
    Amine Moulay Ramdane.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)