Tags: ClickHouse/aws-c-common
Tags
Set thread names, for debugging (awslabs#937) Also, rename a few choice functions where people often think our code is deadlocked, but it's not. Using CamelCase names like "AwsHostResolver" because 15 characters is the max for Linux, so we can't do "aws_host_resolver"
clarify aws_byte_cursor_next_split comments and add tests (awslabs#943) * clarify aws_byte_cursor_next_split comments and add tests
Verify backtrace is defined too, not just header presence (awslabs#935) * Verify backtrace is defined too, not just header presence * clang tidy issues that only just now popped up
Hide symbols from libcrypto.a (awslabs#925) **ISSUE:** We were unable to take the latest version of AWS-LC (source of libcrypto.a). AWS-LC changed the default visibility of symbols in static builds, from "hidden" to "visible" (see aws/aws-lc#466) This resulted in the symbols being visible in whatever shared library or executable ultimately used libcrypto.a. If an application ALSO ended up using libcrypto.so from the system's OpenSSL installation, we'd get crazy crashes due to SOME libcrypto function calls routing through libcrypto.a and SOME function calls routing through libcrypto.so. **SOLUTION:** Adapt the CMake function we use for configuring all C libraries in the Common Runtime ecosystem so that it always hides symbols from libcrypto.a.
improved checks for `-moutline-atomics` (awslabs#909) **Issue #:** awslabs#90 3BB6 2 build failure for iOS that didn't occur until an application was finally linked together. **Description of changes:** Test by compiling a program that actually invokes atomic operations, instead of simply calling `check_c_compiler_flag()`. The errors didn't surface in the empty program CMake uses in `check_c_compiler_flag()` checks.
PreviousNext