Fix case of multiple launcher calls in job script

[rhc54]

When a launcher is invoked multiple times in a job script, each
invocation will have the same "client". The job-level info and tracking
objects are released after each invocation, so we have to recreate them.

Fixes #1211

Signed-off-by: Ralph Castain rhc@pmix.org
(cherry picked from commit 04fd3e7)

[jjhursey]

@dsolt can you confirm that this PR addresses the issue that you were seeing?

[dsolt]

I get this when I run:

Program received signal SIGSEGV, Segmentation fault.
0x000010000081468c in pmix_pointer_array_get_item (table=0x3fffffff8a18, element_index=15)
at /smpi_tmp/dsolt/pmix/pmix-master/src/class/pmix_pointer_array.h:131
131 p = table->addr[element_index];
Missing separate debuginfos, use: debuginfo-install glibc-2.17-222.el7.ppc64le zlib-1.2.7-17.el7.ppc64le
(gdb) print element_index
$1 = 15
(gdb) print table->addr
$2 = (void **) 0x80

I will investigate, but I wanted to provide some status before our weekly meeting

[dsolt]

Oops, I had some v4 pmix/.so files laying around that it was trying to pick up. So, I tested this without our workaround of unsetting everything in the environment and this worked for me!

[rhc54]

woohoo! Thanks