Thanks!
> On Apr 20, 2015, at 6:52 PM, Nathan Hjelm wrote:
>
>
> Fixed in 359a282e7d31a8a7af3a69ead518ff328862b801. mca_base_var does not
> currently allow component to be registered with NULL for both the
> framework and component.
>
> -Nathan
>
> On Mon, Apr 20, 2015 at 04:34:10PM -0600, Ho
I confirmed it is cleaned up for me - thanks Nathan!
On Mon, Apr 20, 2015 at 3:52 PM, Nathan Hjelm wrote:
>
> Fixed in 359a282e7d31a8a7af3a69ead518ff328862b801. mca_base_var does not
> currently allow component to be registered with NULL for both the
> framework and component.
>
> -Nathan
>
> O
Fixed in 359a282e7d31a8a7af3a69ead518ff328862b801. mca_base_var does not
currently allow component to be registered with NULL for both the
framework and component.
-Nathan
On Mon, Apr 20, 2015 at 04:34:10PM -0600, Howard Pritchard wrote:
>Hi Folks,
>Working on master, I"m getting an odd
Tracking it down now. Probably a typo in a component initialization.
-Nathan
On Mon, Apr 20, 2015 at 04:34:10PM -0600, Howard Pritchard wrote:
>Hi Folks,
>Working on master, I"m getting an odd message:
>malloc debug: Request for 1 zeroed elements of size 0 (mca_base_var.c,
>170)
+1 -- I saw this today/over the weekend. I didn't bisect to see where it
started; I assume it was one of the MCA var base updates.
> On Apr 20, 2015, at 6:34 PM, Howard Pritchard wrote:
>
> Hi Folks,
>
> Working on master, I"m getting an odd message:
>
> malloc debug: Request for 1 zeroed
Hi Folks,
Working on master, I"m getting an odd message:
malloc debug: Request for 1 zeroed elements of size 0 (mca_base_var.c, 170)
whenever I launch a job.
It looks like this can be traced back to this line in
orte_ess_singleton_component_register:
mca_base_var_register_synonym(ret "orte", N
