tree a1168eaf956238ad48921fe0f72dd82d1e46b71f
parent 8ede3dd8a19e5bc3db5ba7f7d6b9273f88d2bbee
author Camsyn <camsyn@foxmail.com> 1744646793 +0800
committer GitHub <noreply@github.com> 1744646793 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJn/TKJCRC1aQ7uu5UhlAAA6vEQAD9/EdBGM0e8SQEX3iRLURaC
 pVC3bZwW3SXKrrmYZjNJ+/Cu5shUq1N7QE3Sa6Q6nIU1Zkmot0c9W2lsEM/fVjQm
 es+OhCMVGFkiw8LyB/Ez8QXs7RtGV/g0b/Dam7HavOwwOyZ6oUfzGDRF8ltK1dHj
 MOXhtXOCA5ACr1FDMZ+wu6SRJm67WY4S+fU4Ivoc6EEhbTcjGxVFS3pt8mQ9AMqM
 Yq9d/JiQMosyyQCfYq3aQiuqzpfjM3+S93exQ+zq51OBcrZP5K4pUMe9mbUH0vTn
 a1K+aMqSPZrDwXBvXJRBmCpY+4mnpdkjsk4FygPiJpprspuQPPGaVTonAKLyhOqR
 I5r43FhiJlgEuabK57qlG0yvebJvprjg/s0M6jVKjCxZCpWk5l1OtQoTN9VGxP8J
 XYOKp0ANsPEndF7XVoTIvad3fD64Aqe+Z8sz203BxPVg1TyXq9/yZXKcmJq85oRp
 CrxTK7VLzU08HZ+pr+ktEMrK3RSyKVxTpVw2lW4FUmAb4k+9AUISTJQbZNKDzQJM
 NJnyyy49SaTNrP/AdeguX7/zB1NNQkGUlieg/K4yDWxWg1etzH8g4T1NvZmShhx8
 JP/RnBtxqFUZjXrWseO6iVXlh+f8lKNIREpxDAXqUZIect2DNHqdbNkJAUGgTu4j
 OmB0bb+68o+XMJLFB139
 =T+bk
 -----END PGP SIGNATURE-----
 

[CaptureTracking][NFC] Clarify usage expectations in PointerMayBeCaptured comments (#132744)

Fixes issue #132739.

CaptureAnalysis only considers captures through the def-use chain of the
provided pointer, explicitly excluding captures of underlying values or
implicit captures like those involving external globals.

The previous comment for `PointerMayBeCaptured` did not clearly state
this limitation, leading to its incorrect usage in files such as
ThreadSanitizer.cpp and SanitizerMetadata.cpp.

This PR addresses this by refining the comments for the relevant APIs
within `PointerMayBeCaptured` to explicitly document this behavior.