cpp

Trace the borrow to its owner and last use, then give the consumer an owned snapshot such as std::string instead of the view. Copying a string_view copies only the pointer and length, not the characters, so extending container lifetime or calling reserve does not repair the borrow.

A successful link does not prove ABI compatibility. Macro differences like a PRIVATE compile definition can give producer and consumer different struct layouts, violating ODR silently. Move the definition to PUBLIC on the producing target and compare actual compile commands or preprocessed headers on both sides.

No. TSan detects data races in observed executions but cannot prove an all-atomic ordering protocol is correct. Relaxed operations on separate atomics are race-free yet fail to establish publication; you need a release store and an acquire load that reads it to build the happens-before chain.

A coroutine frame is separate from the lambda closure that created it. Captures live in the closure, so retaining only the returned task leaves the frame referencing a destroyed closure. Pass owning values as by-value parameters of a named coroutine, which are copied into coroutine state before initial suspension.

No, ASan and TSan must run in separate builds. Use ASan plus UBSan for memory reproducers and a separate TSan build with -fsanitize=thread -pthread for races, instrumenting the code under investigation rather than only the test driver.

It does not cover Unreal Engine reflection, RPC, or Gameplay Ability System questions, embedded board initialization, GPU kernels, or general test methodology. Route engine-specific questions to an Unreal skill and general testing practice to a test-driven-development skill.