Tencent / rapidjson / 2025
100%
master: 100%

LAST BUILD BRANCH: id-and-ref
DEFAULT BRANCH: master
Ran
Jobs 2
Files 32
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
2025

Pull #1331

travis-ci

web-flow 
Fix SIGBUS due to unaligned access

Update RAPIDJSON_ALIGN() to always align on an 8-byte boundary
unless otherwise overridden.

On some platforms (such as ARM), 64-bit items (such as doubles and
64-bit integers) must be aligned to an 8 byte address, even though the
architecture is only 32-bits. On these platforms, MemoryPoolAllocator
must match the malloc() behavior and return a 8 byte aligned allocation.
This eliminates any alignment issues that may occur at the expense of
additional memory overhead.

Failure to do so caused a SIGBUS signal when calling
GenericValue::SetNull(). The size of the data_ member of the
GenericValue class is 16 bytes in 32-bit mode and its constructor
requires an 8-byte aligned access.

While parsing a JSON formatted string using Document::ParseStream(), a
stack object containing GenericValue items was constructed. Since the
stack was 8-byte aligned, the constructor calls would succeed. When the
lifetime of the object ends, SetObjectRaw() is invoked. This triggered
an allocation with 4-byte alignment to which the previously 8-byte
aligned GenericValue array was copied. After this, any call to a
GenericValue API that triggered the constructor and thus the placement
new operation on the Data type member would trigger a SIGBUS.

Signed-off-by: Veselin Georgiev <veselin.georgiev@garmin.com>
Signed-off-by: Joshua Watt <Joshua.Watt@garmin.com>
Pull Request #1331: Fix SIGBUS due to unaligned access

5044 of 5048 relevant lines covered (99.92%)

1748568.36 hits per line

Jobs
ID Job ID Ran Files Coverage
11 2025.11 (CONF=debug ARCH=x86 CXX11=ON GCOV_FLAGS='--coverage') 0
99.92
 Travis Job 2025.11
12 2025.12 (CONF=debug ARCH=x86_64 GCOV_FLAGS='--coverage') 0
99.92
 Travis Job 2025.12
Source Files on build 2025
Detailed source file information is not available for this build.