[clang] [compiler-rt] [compiler-rt:ubsan] Add -fsanitize=unaligned-pointer-subtraction to detect undefined subtraction of two pointers (PR #210635)
via cfe-commits
cfe-commits at lists.llvm.org
Sun Jul 19 20:03:39 PDT 2026
github-actions[bot] wrote:
<!--PREMERGE ADVISOR COMMENT: Linux-->
# :penguin: Linux x64 Test Results
* 90466 tests passed
* 1694 tests skipped
* 1 test failed
## Failed Tests
(click on a test name to see its output)
### lldb-api
<details>
<summary>lldb-api.functionalities/gdb_remote_client/TestGdbClientModuleLoad.py</summary>
```
Script:
--
/usr/bin/python3 /home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/dotest.py -u CXXFLAGS -u CFLAGS --env LLVM_LIBS_DIR=/home/gha/actions-runner/_work/llvm-project/llvm-project/build/./lib --env LLVM_INCLUDE_DIR=/home/gha/actions-runner/_work/llvm-project/llvm-project/build/include --env LLVM_TOOLS_DIR=/home/gha/actions-runner/_work/llvm-project/llvm-project/build/./bin --libcxx-include-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/include/c++/v1 --libcxx-include-target-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/include/x86_64-unknown-linux-gnu/c++/v1 --libcxx-library-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/./lib/x86_64-unknown-linux-gnu --triple x86_64-unknown-linux-gnu --build-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/lldb-test-build --lldb-module-cache-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/lldb-test-build/module-cache-lldb/lldb-api --clang-module-cache-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/lldb-test-build/module-cache-clang/lldb-api --executable /home/gha/actions-runner/_work/llvm-project/llvm-project/build/./bin/lldb --lldb-python-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/local/lib/python3.12/dist-packages --compiler /home/gha/actions-runner/_work/llvm-project/llvm-project/build/./bin/clang --dsymutil /home/gha/actions-runner/_work/llvm-project/llvm-project/build/./bin/dsymutil --make /usr/bin/gmake --llvm-tools-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/./bin --lldb-obj-root /home/gha/actions-runner/_work/llvm-project/llvm-project/build/tools/lldb --lldb-libs-dir /home/gha/actions-runner/_work/llvm-project/llvm-project/build/./lib --cmake-build-type Release /home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/functionalities/gdb_remote_client -p TestGdbClientModuleLoad.py
--
Exit Code: 1
Command Output (stdout):
--
Skipping the following test categories: msvcstl, dsym, pdb, gmodules, debugserver, objc
--
Command Output (stderr):
--
PASS: LLDB (/home/gha/actions-runner/_work/llvm-project/llvm-project/build/bin/clang-x86_64) :: test_android_app_process (TestGdbClientModuleLoad.TestGdbClientModuleLoad.test_android_app_process)
--- FileCheck trace (code=1) ---
/home/gha/actions-runner/_work/llvm-project/llvm-project/build/./bin/FileCheck /home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/functionalities/gdb_remote_client/TestGdbClientModuleLoad.py -check-prefix=VDSO
FileCheck input:
[ 0] 98FC07B8 0x0000000000ef0000 [vdso] (0xef0000)
[ 1] 75B11BBB-EF8B-5645-B9B1-A7261EC8ABCF-05413284 0x0000000000ed8ed0 /home/gha/actions-runner/bin/Runner.Worker
FileCheck output:
/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/functionalities/gdb_remote_client/TestGdbClientModuleLoad.py:151:10: error: VDSO: expected string not found in input
# VDSO: [ 0] {{.*}} 0x0000000000ee0000 {{.*}}module_load
^
<stdin>:1:1: note: scanning from here
[ 0] 98FC07B8 0x0000000000ef0000 [vdso] (0xef0000)
^
Input file: <stdin>
Check file: /home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/functionalities/gdb_remote_client/TestGdbClientModuleLoad.py
-dump-input=help explains the following input dump.
Input was:
<<<<<<
1: [ 0] 98FC07B8 0x0000000000ef0000 [vdso] (0xef0000)
check:151'0 { search range start (exclusive)
check:151'1 error: no match found in search range
2: [ 1] 75B11BBB-EF8B-5645-B9B1-A7261EC8ABCF-05413284 0x0000000000ed8ed0 /home/gha/actions-runner/bin/Runner.Worker
check:151'2 } search range end (exclusive)
>>>>>>
FAIL: LLDB (/home/gha/actions-runner/_work/llvm-project/llvm-project/build/bin/clang-x86_64) :: test_vdso (TestGdbClientModuleLoad.TestGdbClientModuleLoad.test_vdso)
Log Files:
- /home/gha/actions-runner/_work/llvm-project/llvm-project/build/lldb-test-build/functionalities/gdb_remote_client/TestGdbClientModuleLoad/Failure_test_vdso.log
======================================================================
FAIL: test_vdso (TestGdbClientModuleLoad.TestGdbClientModuleLoad.test_vdso)
This test checks vdso loading in the situation where the process does
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/functionalities/gdb_remote_client/TestGdbClientModuleLoad.py", line 150, in test_vdso
self.filecheck("image list", __file__, "-check-prefix=VDSO")
File "/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2760, in filecheck
self.assertEqual(cmd_status, 0)
AssertionError: 1 != 0
Config=x86_64-/home/gha/actions-runner/_work/llvm-project/llvm-project/build/bin/clang
----------------------------------------------------------------------
Ran 2 tests in 0.133s
FAILED (failures=1)
--
```
</details>
If these failures are unrelated to your changes (for example tests are broken or flaky at HEAD), please open an issue at https://github.com/llvm/llvm-project/issues and add the `infrastructure` label.
https://github.com/llvm/llvm-project/pull/210635
More information about the cfe-commits
mailing list