Steve,
This is indeed strange. The mechanism you describe works for me.
Here is my simple test :
-- mpi-sig.c --
#include "mpi.h"
#include
#include
void warn(int sig) {
printf("Got signal %d\n", sig);
}
int main (int argc, char ** argv) {
Could be a bug on our part. If you --enable-debug in your configure, you can
then set -mca odls_base_verbose 5 and (amidst a lot of other stuff) you'll see
the signal being delivered to the proc if you sent it to mpirun.
If you send the signal direct to the proc yourself, we shouldn't touch
it.
On 08/25/2010 12:43 PM, Ralph Castain wrote:
On Aug 25, 2010, at 11:26 AM, Steve Wise wrote:
On 08/25/2010 11:33 AM, Ralph Castain wrote:
We don't use it - mpirun traps it and then propagates it by default to all
remote procs.
So I should send the signal to the mpirun pro
On Aug 25, 2010, at 11:26 AM, Steve Wise wrote:
> On 08/25/2010 11:33 AM, Ralph Castain wrote:
>> We don't use it - mpirun traps it and then propagates it by default to all
>> remote procs.
>>
>>
>
> So I should send the signal to the mpirun process?
Yes - however, note that it will be pro
On 08/25/2010 11:33 AM, Ralph Castain wrote:
We don't use it - mpirun traps it and then propagates it by default to all
remote procs.
So I should send the signal to the mpirun process?
What OMPI version is this?
1.4.1
On Aug 25, 2010, at 10:23 AM, Steve Wise wrote:
Hey
We don't use it - mpirun traps it and then propagates it by default to all
remote procs.
What OMPI version is this?
On Aug 25, 2010, at 10:23 AM, Steve Wise wrote:
> Hey Open MPI wizards,
>
> I'm trying to debug something in my library that gets loaded into my mpi
> processes when they are st
Hey Open MPI wizards,
I'm trying to debug something in my library that gets loaded into my mpi
processes when they are started via mpirun. With other MPIs, I've been
able to deliver SIGUSR2 to the process and trigger some debug code I
have in my library that sets up a handler for SIGUSR2. Ho
