pcp
[Top] [All Lists]

Re: [pcp] pmcd dumping core - multiple issues

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pmcd dumping core - multiple issues
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Sun, 28 Jul 2013 02:28:13 -0400 (EDT)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <51F44856.3090308@xxxxxxxxxxxxxxxx>
References: <51F44856.3090308@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: eNvfn4/4S3MJu1Lywv8FIuBw3KO7Xg==
Thread-topic: pmcd dumping core - multiple issues
Hi Ken,

----- Original Message -----
> I am seeing qa/183 failing across lots of hosts in a full run, i.e. $
> check (no args)
> ...
> [Sun Jul 28 07:08:46] pmcd(23023) Error: Unexpected signal 11 ...
> 
> Dumping to core ...
> 
> Now this is a non-negotiable release blocker.

*nod* ... any pmcd failure is #1 priority as far as I'm concerned.

> pmcd is not allowed to dump core ... we're spent 10 years getting to
> this point, and we're going to keep it that way.

Yep, it needs to be fixed post-haste, and any reproducible test case
is extremely helpful.  Will be digging further into it tomorrow, and
I hope others are too ... any/all info is helpful, even if its not a
fix (just "I'm observing it in situation X is useful).

> And finally we've lost the procedure call traceback ... the relevant

I noticed that too :( ... not very helpful.

> code is guarded by
> #if HAVE_TRACE_BACK_STACK
> but NOTHING appears to define HAVE_TRACE_BACK_STACK under any
> circumstances ... can anyone explain what happened here?

Not sure, I don't recall touching this code ... but have a vague
memory that it may have been IRIX-specific?

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>