[
https://issues.apache.org/jira/browse/LOGCXX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Frost updated LOGCXX-322:
Attachment: 130-bugfix-LOGCXX-322.dpatch
> Crashes on exit from multithreaded program using log4cxx
[
https://issues.apache.org/jira/browse/LOGCXX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934848#comment-13934848
]
Tobias Frost commented on LOGCXX-322:
-
Hi, Ubuntu has appled the patch (via here
http
[
https://issues.apache.org/jira/browse/LOGCXX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934889#comment-13934889
]
Thorsten Schöning commented on LOGCXX-322:
--
Thanks for the patch, I think we alre
Author: tschoening
Date: Fri Mar 14 11:40:27 2014
New Revision: 1577488
URL: http://svn.apache.org/r1577488
Log:
LOGCXX-430: LogManager::getRootLogger is not thread-safe
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/cpp/logmanager.cpp
incub
[
https://issues.apache.org/jira/browse/LOGCXX-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Schöning resolved LOGCXX-430.
--
Resolution: Fixed
Fix Version/s: 0.10.1
I applied my patch because no one object
Tobias Frost created LOGCXX-431:
---
Summary: When log4cxx creates a thread, it doesn't block signals
it's not using, leading to unreliable signal delivery for the calling process.
Key: LOGCXX-431
URL: https://issues.a