You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Kenta Murata (Jira)" <ji...@apache.org> on 2021/02/18 06:38:00 UTC

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

Kenta Murata created ARROW-11686:
------------------------------------

             Summary: [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


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)