activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Martens (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-203) Segmentation Fault in Integration tests occurs occasionally.
Date Mon, 10 Nov 2008 08:56:05 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47202#action_47202
] 

Alexander Martens commented on AMQCPP-203:
------------------------------------------

Hi!

Concerning the weekend test, another segmentation fault was observed a few hours later, again
at
(*c->plain_cleanup_fn)((void *)c->data);

And yes *c is

(gdb) p *c
$1 = {next = 0x0, data = 0x0, plain_cleanup_fn = 0xfffffffe, child_cleanup_fn = 0}

if we go upwards, until 
#3  0x4057abdb in apr_thread_exit (thd=0x91324a0, retval=0) at threadproc/unix/thread.c:206
206         apr_pool_destroy(thd->pool);

We can do some prints that I'm not sure how interesting they might actually be:

(gdb) p *thd
$6 = {pool = 0x41800b90, td = 0x91324b8, data = 0x4150d3e0, func = 0x4030586e <decaf::lang::Thread::runCallback(apr_thread_t*,
void*)>, exitval = 0}

(gdb) p *thd->pool
$7 = { parent = 0x41800b90, child = 0x91f5688, sibling = 0x41800b90, ref = 0x1, cleanups =
0x40000400, free_cleanups = 0xc2694000, allocator = 0x86ba7290, subprocesses = 0x0, abort_fn
= 0, user_data = 0x0, tag = 0x0, active = 0x0, self = 0x0, self_first_avail = 0x0, pre_cleanups
= 0x0, free_pre_cleanups = 0x0}

(gdb) p *thd->pool->child
$8 = {parent = 0x1, child = 0x0, sibling = 0x41800b58, ref = 0x1, cleanups = 0x0, free_cleanups
= 0x1, allocator = 0x41800b14, subprocesses = 0x1, abort_fn = 0, user_data = 0x0, tag = 0x0,
active = 0x0, self = 0x0, self_first_avail = 0x0, pre_cleanups = 0x0, free_pre_cleanups =
0x0}

(gdb) p *thd->pool->child->sibling
$9 = {parent = 0xfffffffe, child = 0x0, sibling = 0x0, ref = 0x0, cleanups = 0x0, free_cleanups
= 0x0, allocator = 0x0, subprocesses = 0x0, abort_fn = 0, user_data = 0x0, tag = 0x0, active
= 0x0, self = 0x0, self_first_avail = 0x0, pre_cleanups = 0x41800b90, free_pre_cleanups =
0x91f5688}

Don't know if this says somethign to you. On $7, parent==sibling looks awkward to me. In $8
and $9 parent seems to be sick.


> Segmentation Fault in Integration tests occurs occasionally.
> ------------------------------------------------------------
>
>                 Key: AMQCPP-203
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-203
>             Project: ActiveMQ C++ Client
>          Issue Type: Sub-task
>          Components: Integration Tests
>    Affects Versions: 2.2.1
>         Environment: CentOS 5.2 / REHL / Fedora 9
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 2.2.2
>
>         Attachments: BufferedInputStream.cpp.patch, segfault.6517.tar.gz, segfault.bufferedinputstream.log.gz,
segfaults.barak.tar.gz, segfaults.tar.gz, weekend.puzzle.tar.gz
>
>
> While running the integration tests in a long loop an occasional Segmentation fault has
been seen. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message