You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Weston Pace (Jira)" <ji...@apache.org> on 2021/03/31 13:54:00 UTC

[jira] [Created] (ARROW-12167) [C++] Dump threads on signal

Weston Pace created ARROW-12167:
-----------------------------------

             Summary: [C++] Dump threads on signal
                 Key: ARROW-12167
                 URL: https://issues.apache.org/jira/browse/ARROW-12167
             Project: Apache Arrow
          Issue Type: Improvement
          Components: C++
            Reporter: Weston Pace


This may be wishful thinking but in Java there is a signal handler for SIGQUIT which dumps the equivalent of GDB's "thread apply all bt" to standard out (maybe err).

This is incredibly useful for debugging deadlocks.  For example, in the R builds we may be introducing a timeout (ARROW-12143) and if the build times out during a test run we could use this utility to dump what it was trying to do.  Otherwise I'm not sure github actions allows ptrace so the gdb route is off the table.


It's also easy enough that users (who might be intimidated by being asked for a core file or attaching gdb) can usually handle it.

Technically speaking, I have no idea if it is possible.



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