title: How to identify the full command that caused the crash from the core dump file
body: <p>There is a problem to identify the full command from the core dump file using gdb
  The crashed  command itself can be long</p>
  <p>i.e.</p>
  <pre><code>myCommand -f log/SlaRunTimeReport.rep -I input/myFile.txt -t output/myFile.txt
  </code></pre>
  <p>But When using gdb to identify the command in the location “Core was generated by”</p>
  <p>i.e. by executing</p>
  <pre><code>gdb -c core.56536
  </code></pre>
  <p>The Output:</p>
  <pre><code>GNU gdb (GDB) Red Hat Enterprise Linux 7.10-20.el7
  
  ….
  
  Core was generated by `myCommand -f log/SlaRunTimeReport.rep -I 
  input/myFile.t'.
  </code></pre>
  <p>It is possible to see that the full command(executable + parameters)  was cut in the middle</p>
  <pre><code>‘myCommand -f log/SlaRunTimeReport.rep -I input/myFile.t'
  </code></pre>
  <p>In additional using <strong>strings</strong> command , also did not help to identify the full command</p>
  <pre><code>strings core.56536 | grep PMRunTimeReport
  </code></pre>
  <p>The Output:</p>
  <pre><code>myCommand 
  
  myCommand -f log/SlaRunTimeReport.rep -I input/myFile.t
  </code></pre>
  <p>Is there any way to get from coredump file the full command that caused the failure</p>
  <p>Thanks in Advance</p>