[jira] [Resolved] (ARROW-11686) [C++]flight-test-integration-client sometimes exits by SIGABRT but does not print the stack trace

["David Li (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-11686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Li resolved ARROW-11686.
------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 9524
[https://github.com/apache/arrow/pull/9524]

> [C++]flight-test-integration-client sometimes exits by SIGABRT but does not print the stack trace
> -------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-11686
>                 URL: https://issues.apache.org/jira/browse/ARROW-11686
>             Project: Apache Arrow
>          Issue Type: Test
>          Components: C++
>            Reporter: Kenta Murata
>            Assignee: Kenta Murata
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> I found that flight-test-integration-client sometimes exits by SIGABRT.
> This problem has been caused at the commit https://github.com/apache/arrow/commit/848c803bf162dca2e31cb63fbb3d2f9dbdda460e on the master branch, but the change in the commit seems unrelated to this problem.
> To investigate this problem, I would like to let this command show the stack trace when it exits by SIGABRT.  It should be done by calling {{ArrowLog::InstallFailureSignalHandler}} function in the main function.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)