incubator-celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ewout Ros (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CELIX-103) log_service segfault on bundle stop/destroy
Date Thu, 19 Dec 2013 14:20:08 GMT

    [ https://issues.apache.org/jira/browse/CELIX-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852915#comment-13852915
] 

Ewout Ros edited comment on CELIX-103 at 12/19/13 2:19 PM:
-----------------------------------------------------------

This patch places apr_thread_join after the apr_thread_mutex_unlock functions

apr_thread_join was called before all the thread mutexes were unlocked, which resulted in
a deadlock


was (Author: ewout.ros):
This patch places apr_thread_join after the apr_thread_mutex_unlock functions

> 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
>            Priority: Critical
>         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.4#6159)

Mime
View raw message