[
https://issues.apache.org/jira/browse/HBASE-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122169#comment-16122169
]
Enis Soztutar commented on HBASE-18541:
---------------------------------------
bq. The following command doesn't print stack trace when test fails:
When the program crashes, there is usually a core dump file. You can use gdb to
get the stack trace. You can use something like:
{code}
gdb ./buck-out/gen/core/multi-retry-test core.XXX
{code}
Then within gdb, you can use {{bt}} or {{thread apply all bt}} to get the
backtrace.
> [C++] Segfaults from JNI
> ------------------------
>
> Key: HBASE-18541
> URL: https://issues.apache.org/jira/browse/HBASE-18541
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Ted Yu
>
> retry-test and multi-retry-test fails flakily when run with
> {code}
> buck test --all --no-results-cache
> {code}
> or when run in a loop:
> {code}
> for i in `seq 1 10`; do buck test --no-results-cache core:retry-test || break
> 1; done
> {code}
> The problem seems to be within the JNI internals and usually happens at the
> create table method call. I was not able to inspect much, but the comments in
> our mini-cluster indicate that we may need to use global references instead
> of local ones. I suspect the problem happens when there is a GC run for the
> test since the failure happens usually after some time (but almost always in
> create table method).
> [~ted_yu] do you mind taking a look at this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
