Charm++ parallel programming system

[Jozsef Bakosi <jbakosi AT lanl.gov>]

Hi folks,

I'm trying to use randomized queues to test the correctness of my asynchronous
logic. In a section of my code I have a set of chare array elements making
cklocalBranch()-> calls to group branches on their PE which then spawn
point-to-point communications to each other to exchange information. From the
array elements, I start two sets of these cklocalBranch()-> calls after each
other, and both of these paths of execution end up in a similar communication
pattern using point-to-point entry method calls among multiple group branches 
to
different entry methods.

This logic is correct with the default queue, but causes a hang with 
randomized
queues. I guess since the randomized queue schedules messages randomly, so 
some
entry methods are instructed to be called (i.e. put in the queue) but never 
end
up called. I verified that this is the case with simple printouts: correctly
called but with, e.g., Group::thisProxy[ otherPE ].fn(), but fn() on the 
otherPE
does not always gets called, i.e., not on all PEs as it should be, only on 
some
of the PEs called.

My questions:

1. Can I expect two simultaneous sets of point-to-point entry method calls
(targeting different entry methods) on the same group to perform correctly 
with
randomized queues?

2. I have tried charmdebug but I only get

ParDebug> [...]/charmrun +p4 [...]/pgm <opts> +cpd +DebugDisplay 
127.0.1.1:0.0 ++server +DebugSuspend
ParDebug> Error executing [...]/charmrun +p4 [...]/pgm <opts> +cpd 
+DebugDisplay 127.0.1.1:0.0 ++server +DebugSuspend

The charmdebug documentation says: "charmdebug command line launching only 
works
on net-*, netlrts-*, and verbs-* builds of Charm++" Does charmdebug work with
the MPI backend?

3. Is there a way to look at the queues somehow?

Thanks,
Jozsef
-- 
Jozsef Bakosi
Computational Physics and Methods (CCS-2)
Los Alamos National Laboratory