charm AT lists.siebelschool.illinois.edu
Subject: Charm++ parallel programming system
List archive
- From: Jozsef Bakosi <jbakosi AT lanl.gov>
- To: charm <charm AT lists.cs.illinois.edu>
- Subject: [charm] Deadlock detection
- Date: Tue, 26 Jun 2018 17:03:54 -0600
- Authentication-results: illinois.edu; spf=pass smtp.mailfrom=jbakosi AT lanl.gov; dmarc=pass header.from=lanl.gov
Hi folks,
Time to time I run into asynchronous logic errors (that I'm pretty sure are my
fault) that non-deterministically produce deadlocks without an error message.
I wonder what tools I have available that I can use to diagnose such problems.
Somehow, it would be great if I could detect from the runtime system that some
messages are being waited on, but nothing really happens in which case I could
dump some messages and their labels/ids/etc, that would help identify at least
what entry methods are waiting for messages, or something similar.
What do you suggest? How do you deal with such errors?
Thanks,
Jozsef
- [charm] Deadlock detection, Jozsef Bakosi, 06/26/2018
- Message not available
- Re: [charm] Deadlock detection, Jozsef Bakosi, 06/26/2018
- Message not available
- Re: [charm] Deadlock detection, Jozsef Bakosi, 06/27/2018
- Re: [charm] Deadlock detection, Phil Miller, 06/27/2018
- Re: [charm] Deadlock detection, Jozsef Bakosi, 06/28/2018
- Re: [charm] Deadlock detection, Kale, Laxmikant V, 06/29/2018
- Re: [charm] Deadlock detection, Jozsef Bakosi, 06/28/2018
- Re: [charm] Deadlock detection, Phil Miller, 06/27/2018
- Re: [charm] Deadlock detection, Jozsef Bakosi, 06/27/2018
- Message not available
- Re: [charm] Deadlock detection, Jozsef Bakosi, 06/26/2018
- Message not available
Archive powered by MHonArc 2.6.19.