[Bug]: Missing constructor for `absl::synchronization_internal::KernelTimeout` in shared builds about abseil-cpp HOT 5 CLOSED

Does the patch proposed in #1624 (comment) fix the problem? That would be a hint that this is actually the same issue as #1624.

from abseil-cpp.

Does the patch proposed in #1624 (comment) fix the problem? That would be a hint that this is actually the same issue as #1624.

We ran into this problem with the patched abseil. There are three possibilities as far as I can see:

• the patch is independent of the bug
• the patch uncovered the bug
• the patch introduced the bug

I still think that it's very closely related, because of the way how constructors/destructors are (apparently) missing in the shared library.

However, it is not the same in the sense that the tensorflow builds do set NDEBUG.

from abseil-cpp.

@derekmauro, what do you think about the situation here now? I get that you'd like constructurs/destructors to be inlined as much as possible, but given that synchronization_internal::KernelTimeout is used from another library (absl_mutex), this doesn't work in shared builds.

from abseil-cpp.

I haven't had time to look into this, sorry.

from abseil-cpp.

Yeah, it's OK. I managed to dig a bit more and found it's an interaction between bazel/tensorflow and their vendored abseil. I'll close this, as there's nothing to do for abseil AFAICT.

from abseil-cpp.