Hi Nguyen,
Yes, I will use this information and check this. Maybe some sort of internal
length check is needed in order to prevent this kind of assert.
Thanks
Lennart
From: Nguyen Luu
Sent: den 1 juni 2018 09:55
To: Lennart Lund
Cc: opensaf-devel@lists.sourceforge.net
Subject: Re: [PATCH
Hi Nguyen,
I will send out a new review request as you suggest. I will probably not be
able to do this today
I also would like to understand why you get a coredump. I cannot reproduce that
problem in my environment also it does not happen in Osaftest or CoreMW test.
The imm_modify_config has
In the methods LogAgent::saLogStreamClose() and LogAgent::saLogWriteLogAsync(),
the client is deleted if failed to recover; however, the pointer to the log
stream of this client has not been reseted. Therefore, when the destrustor of
ScopeData runs, the reference counter could be restored on
Summary: log: restore ref counter for deleted stream [#2870]
Review request for Ticket(s): 2870
Peer Reviewer(s): Lennart, Canh
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop, release
Development branch: ticket-2870
Base revision:
Hi Lennart,
I've run *test_ccbhdl* in OpenSAF UML cluster and the same core dump was
still generated as described in my previous mail.
My UML cluster was built and installed with the latest OpenSAF develop
commit (*5d8d104 rded: run controller promotion code in new thread
[#2857]*), and with
