Bug 275892 - Adding -fsanitize=fuzzer,address on main-amd64-default causes the link failure: ld: error: undefined symbol: __sanitizer::ThreadArgRetval::GetAllPtrsLocked(__sanitizer::InternalMmapVector<unsigned long>*)
Summary: Adding -fsanitize=fuzzer,address on main-amd64-default causes the link failur...
Status: Closed DUPLICATE of bug 275854
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-toolchain (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-22 19:59 UTC by Yuri Victorovich
Modified: 2023-12-22 23:51 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer freebsd_triage 2023-12-22 19:59:34 UTC 
The port www/wabt (version 1.0.33_1) builds the executable wasm2wat-fuzz with -fsanitize=fuzzer,address.

The build fails on main-amd64-default:

> /usr/bin/c++ -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing  -isystem /usr/local/include -Wold-style-cast -fno-exceptions -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing  -isystem /usr/local/include  -DNDEBUG -fstack-protector-strong -L/usr/local/lib    -fsanitize=fuzzer,address CMakeFiles/wasm2wat-fuzz.dir/src/tools/wasm2wat-fuzz.cc.o -o wasm2wat-fuzz  -Wl,-rpath,/wrkdirs/usr/ports/www/wabt/work/.build:  libwabt-fuzz.so  libwabt.so  /usr/lib/libcrypto.so && :
> ld: error: undefined symbol: __sanitizer::ThreadArgRetval::GetAllPtrsLocked(__sanitizer::InternalMmapVector<unsigned long>*)


Log: https://pkg-status.freebsd.org/beefy18/data/main-amd64-default/p95fa05afac27_seac3646fcd/logs/wabt-1.0.33_1.log
Comment 1 Dimitry Andric freebsd_committer freebsd_triage 2023-12-22 21:40:05 UTC 
Looks like a dupe of bug 275854? I fixed that one in https://cgit.freebsd.org/src/commit/?id=0c3af23961e170538f375c392b043903c1397780 (2023-12-20 16:08:26 +0000).
Comment 2 Yuri Victorovich freebsd_committer freebsd_triage 2023-12-22 23:51:58 UTC 
Yes, it looks like a duplicate.

Thank you.

*** This bug has been marked as a duplicate of bug 275854 ***