You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@celix.apache.org by "Alexander Broekhuis (JIRA)" <ji...@apache.org> on 2014/01/07 08:10:51 UTC
[jira] [Resolved] (CELIX-103) log_service segfault on bundle
stop/destroy
[ https://issues.apache.org/jira/browse/CELIX-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Broekhuis resolved CELIX-103.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0-incubating
Assignee: Alexander Broekhuis (was: Alexander Broekhuis)
Applied patch and updated error handling. Please verify and close if ok. Thanks for your work!
----------------------------
Author: abroekhuis
Date: Tue Jan 7 07:07:39 2014
New Revision: 1556126
URL: http://svn.apache.org/r1556126
Log:
CELIX-103: Applied patch and updated code to have better error handling.
> log_service segfault on bundle stop/destroy
> -------------------------------------------
>
> Key: CELIX-103
> URL: https://issues.apache.org/jira/browse/CELIX-103
> Project: Celix
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Environment: OS: Centos 6.4 Linux (64 bit), APR 1.4.6
> Reporter: Ewout Ros
> Assignee: Alexander Broekhuis
> Priority: Critical
> Fix For: 1.0.0-incubating
>
> Attachments: log_service_apr.patch
>
>
> Stopping/destroying the log_service bundle (manually or at framework stop) causes a segfault when the log_writer is still 'Active'. When the log_writer is stopped first, the log_service bundle can be stopped without problems.
> The segfault occurs in the Unwind ForcedUnwind() function in the libgcc library, called by pthread_exit().
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)