Fix to be able to get stacktrace

[arukuka]

Summary

Fixed an issue where stack traces could not be obtained properly in CC.

Purpose

stack trace is important information

Contents

• Use backtrace instead of addr2line
• Add --strip=never option at bazel build
• Remove unnecessary code

Testing Methods Performed

I used qmpc::Log::Debug in several places and confirmed that a stack trace could be obtained as follows.

• example of insertion:

  diff --git a/src/ComputationContainer/ConfigParse/ConfigParse.hpp b/src/ComputationContainer/ConfigParse/ConfigParse.hpp
  index 5e4647c4..3361ff3a 100644
  --- a/src/ComputationContainer/ConfigParse/ConfigParse.hpp
  +++ b/src/ComputationContainer/ConfigParse/ConfigParse.hpp
  @@ -83,6 +83,7 @@ class Config
   
       Config()
       {
  +        qmpc::Log::Debug(__FILE__, __LINE__);
           party_id = getEnvInt("PARTY_ID");
           n_parties = getEnvInt("N_PARTIES");
           sp_id = getEnvInt("SP_ID");

• log:

  root@dae2cfbfc368:/QuickMPC# ./bazel-bin/computation_container
  2022-08-18 01:22:46+0000|DEBUG|Config::Config() at ./ConfigParse/ConfigParse.hpp:86|./ConfigParse/ConfigParse.hpp|86
  [2022-08-18 01:22:46.757] [info] 3 maps to http://computation_container3:50120 and http://computation_container3:50120
  [2022-08-18 01:22:46.757] [info] 1 maps to http://computation_container1:50120 and http://computation_container1:50120
  ...

[watason]

it looks good.
By the way, what were the cause of these, if u could find out?
Also, i have a request.
please create a new issue ( with completed state ), and link to this PR.
thank you.

[mdonaka]

Thanks for fixing it. Approve if CI passes.

[arukuka]

@watason
Noted with thanks.
I created an issue, and linked it.
I think that it is appropriate to close the issue above by merging this pull request, so I am leaving it not completed state but open.

By the way, what were the cause of these, if u could find out?

I have not correctly understood the cause in detail, but I left a work log in the issue, so please check it.