Thanks for the fix.
-- Josh
On Feb 16, 2009, at 2:59 PM, George Bosilca wrote:
Josh,
Spending few minutes to understand, could have pinpointed you to
the real culprit: the tool itself!
The assert in the code state that on finalize there is still a
registered signal handler. A quick gdb s
Never mind -- you just did. Thanks! :-)
On Feb 16, 2009, at 3:07 PM, Jeff Squyres wrote:
George --
Will you commit?
On Feb 16, 2009, at 2:59 PM, George Bosilca wrote:
Josh,
Spending few minutes to understand, could have pinpointed you to
the real culprit: the tool itself!
The assert
George --
Will you commit?
On Feb 16, 2009, at 2:59 PM, George Bosilca wrote:
Josh,
Spending few minutes to understand, could have pinpointed you to the
real culprit: the tool itself!
The assert in the code state that on finalize there is still a
registered signal handler. A quick gdb s
Josh,
Spending few minutes to understand, could have pinpointed you to the
real culprit: the tool itself!
The assert in the code state that on finalize there is still a
registered signal handler. A quick gdb show that this is for the
SIG_CHLD. Tracking the signal addition in the tool (bre
This commit seems to have broken the tools. If I use orte-ps then on
finalize I get an abort() with the following stack:
shell$ orte-ps
...
(gdb) bt
#0 0x2bcee155 in raise () from /lib64/libc.so.6
#1 0x2bcefbf0 in abort () from /lib64/libc.so.6
#2 0x2bce75d6 in __asse