- **status**: review --> fixed
- **Comment**:
commit 84e73242dca86ac6d4318e7351e5b45128da6101 (HEAD -> develop,
origin/develop, ticket-3002)
Author: Vu Minh Nguyen <vu.m.ngu...@dektech.com.au>
Date: Mon Feb 11 15:40:31 2019 +0700
log: fix coredump at log agent application [#3002]
There is a race in using singleton-static class object b/w mds thread
and application thread - caller of exit() api.
This patch still uses singleton but making the instance shared_ptr
to ensure the resource will not be destroyed if it is being used.
---
** [tickets:#3002] log: coredump at log agent upon application exit**
**Status:** fixed
**Milestone:** 5.19.03
**Created:** Tue Jan 22, 2019 07:06 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Jan 24, 2019 10:15 AM UTC
**Owner:** Vu Minh Nguyen
**Attachments:**
-
[loga_coredump_bt.txt](https://sourceforge.net/p/opensaf/tickets/3002/attachment/loga_coredump_bt.txt)
(8.1 kB; text/plain)
Log application got a coredump at the log agent code - mutex unlock failed with
error code EINVAL (22). This bug is very much similar to the ticket [#2860].
See the attached full back trace.
There is a singleton log agent object (LogAgent) which is declared as static
and due to order of desctructor upon the program exit, the memory allocated for
mutex might be destroyed before mutex unlock is called.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list._______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
