title: Message "During startup program terminated with signal SIGKILL" from GDB
body: <p>I'm having trouble debugging a C++ program on AIX built with GNU tools. When the program runs outside the debugger:</p>
  
  <pre><code>-bash-4.3$ ./cryptestcwd v
  Segmentation fault (core dumped)
  </code></pre>
  
  <p>When the program runs under GDB, the debugger prints the message <em><code>During startup program terminated with signal SIGKILL, Killed.</code></em> and exits:</p>
  
  <p><a href="https://i.stack.imgur.com/oSOgN.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/oSOgN.png" alt="enter image description here"></a></p>
  
  <p>An added wrinkle is, this only happens with an <a href="https://github.com/noloader/cryptopp-autotools" rel="nofollow noreferrer">Autotools front-end</a>. It does not happens with our regular GNUmakefile. We supply the same arguments to both Autotools and the GNUmakefile. We are aware Autotools <a href="https://stackoverflow.com/q/47315717/608639">adds additional options</a> and even <a href="https://stackoverflow.com/q/47315717/608639">adds C files</a> to the C++ project, but we have no control over it.</p>
  
  <p>A related question is at <a href="https://stackoverflow.com/q/16416866/608639">During startup program terminated with signal SIGKILL, Killed</a>, but it does not have useful answers. Two other related questions just state that <code>SIGKILL</code> cannot be caught. Also see <a href="https://stackoverflow.com/q/25325847/608639">Debugging program that catches SIGKILL under Linux</a> and <a href="https://stackoverflow.com/q/23826676/608639">Handling signals with gdb</a>.</p>
  
  <p>How can I debug the problem further?</p>