This is a very useful flag for debugging, can get a backtrace on demand from a triggering VLOG statement. Right now it doesn't seem to be hooked up in our source. No Abseil C++ logging as of yet, but since we didn't seem to really "need" this for so long, a little unclear how to prioritize, but I wanted to file a bug to track nonetheless.
Ideally we'd have --log_backtrace_at=file.cc:50 flag trigger the backtrace when that VLOG statement in file.cc line 50 was logged if we do want to patch this up.
|
ABSL_CONST_INIT std::atomic<size_t> log_backtrace_at_hash{0}; |
This is a very useful flag for debugging, can get a backtrace on demand from a triggering VLOG statement. Right now it doesn't seem to be hooked up in our source. No Abseil C++ logging as of yet, but since we didn't seem to really "need" this for so long, a little unclear how to prioritize, but I wanted to file a bug to track nonetheless.
Ideally we'd have
--log_backtrace_at=file.cc:50flag trigger the backtrace when that VLOG statement in file.cc line 50 was logged if we do want to patch this up.xls/xls/common/logging/log_message.cc
Line 334 in 56a46a1