Uploaded image for project: 'Apache Arrow'
  1. Apache Arrow
  2. ARROW-11686

[C++]flight-test-integration-client sometimes exits by SIGABRT but does not print the stack trace

    XMLWordPrintableJSON

Details

    • Test
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.0.0
    • C++

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              mrkn Kenta Murata
              mrkn Kenta Murata
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h 20m
                  1h 20m