[jira] [Closed] (CELIX-198) Logging can segfault for strings 512 characters or longer

2015-01-08 Thread Daniel Parker (JIRA)
[ https://issues.apache.org/jira/browse/CELIX-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Parker closed CELIX-198. --- logging long messages no longer causes any segfaults > Logging can segfault for strings 512 characters or

[jira] [Resolved] (CELIX-198) Logging can segfault for strings 512 characters or longer

2015-01-08 Thread Alexander Broekhuis (JIRA)
[ https://issues.apache.org/jira/browse/CELIX-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Broekhuis resolved CELIX-198. --- Resolution: Fixed Updated the log_command to determine the length and use snprintf. --

svn commit: r1650294 - in /celix/trunk: log_writer/log_writer_stdout/private/src/ remote_services/calculator_proxy/private/src/ remote_services/calculator_proxy2/private/src/ remote_services/remote_se

2015-01-08 Thread abroekhuis
Author: abroekhuis Date: Thu Jan 8 14:29:38 2015 New Revision: 1650294 URL: http://svn.apache.org/r1650294 Log: CELIX-198: Updated log_command to determine message length, and use snprintf to prevent overflows. Modified: celix/trunk/log_writer/log_writer_stdout/private/src/log_writer_stdout