Unable to get stacktrace with debug infomation in ComputationContainer

[arukuka]

Logger qmpc::Log::Debug needs to print information about the place which calls this function via boost::stacktrace.
However, it prints only address and binary file location at the moment.
This issue could be reproduced with a following patch.

• patch

  diff --git a/src/ComputationContainer/ConfigParse/ConfigParse.hpp b/src/ComputationContainer/ConfigParse/ConfigParse.hpp
  index 5e4647c4..28324e8c 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");

• result

  root@dae2cfbfc368:/QuickMPC# ./bazel-bin/computation_container
  2022-08-18 04:28:28+0000|DEBUG|0x00005649CF12504B in ./bazel-bin/computation_container|./ConfigParse/ConfigParse.hpp|86
  ...

We referred to the following document for how to use "boost::stacktrace".

• https://www.boost.org/doc/libs/1_80_0/doc/html/stacktrace.html
• In particular,
  • for coding: https://www.boost.org/doc/libs/1_80_0/doc/html/stacktrace/getting_started.html
  • for compile, link options: https://www.boost.org/doc/libs/1_80_0/doc/html/stacktrace/configuration_and_build.html

We confirmed that a stack trace can be obtained with a simple program without using bazel.

[arukuka]

• Debugging C++ on MacOS does not work bazelbuild/bazel#6327
  • spawn_strategy option seem not to be related.
  • strip option, I missed it, which maybe related.

[arukuka]

• Not getting line numbers with addr2line boostorg/stacktrace#97
  • I tried using backtrace

Fixed	--spawn_strategy=local	--strip=never	backtrace
o	o	o	o
o	x	o	o
x	x	x	o
x	x	o	x

[arukuka]

This issue can be resolved if src/ComputationContainer/ComputationParty/BUILD has following configuration.

diff --git a/src/ComputationContainer/ComputationParty/BUILD b/src/ComputationContainer/ComputationParty/BUILD
index 6f956f6c..3d1f8aef 100644
--- a/src/ComputationContainer/ComputationParty/BUILD
+++ b/src/ComputationContainer/ComputationParty/BUILD
@@ -14,5 +14,8 @@ cc_library(
         "//Job:jobManager",
         "//LogHeader:logger",
     ],
+    linkopts=["-lboost_stacktrace_backtrace", "-ldl", "-lbacktrace"],
+    defines=["BOOST_STACKTRACE_LINK",
+        "BOOST_STACKTRACE_USE_BACKTRACE"],
     visibility = ["//visibility:public"],
 )

I checked the difference of bazel-bin/computation_container-2.params before and after applying the above patch.
bazel-bin/computation_container-2.params is used for link option, it could be checked by bazel build -s //:computation_container.
Then, I found a setting in a place not related to logging.

QuickMPC/src/ComputationContainer/Job/BUILD

Lines 15 to 18 in b173bce

	linkopts=["-lboost_stacktrace_addr2line"],
	defines=["BOOST_STACKTRACE_LINK",
	"BOOST_STACKTRACE_USE_ADDR2LINE"],

Removing this one, the configuration in src/ComputationContainer/ComputationParty/BUILD above is no longer needed.