aboutsummaryrefslogtreecommitdiff
path: root/llvm/docs/CommandGuide/llvm-remarkutil.rst
diff options
context:
space:
mode:
authorBlue Gaston <bblueconway@gmail.com>2023-04-06 10:33:40 -0700
committerBlue Gaston <bblueconway@gmail.com>2023-04-07 14:56:06 -0700
commit0f9bfe0a02ffff077a1a98065069b52744e31723 (patch)
tree18d729e3a2170f7226420f160d64591d0bcd0c11 /llvm/docs/CommandGuide/llvm-remarkutil.rst
parent5315ca696169ae015b5aa56ab6c27aca21d633f7 (diff)
downloadllvm-0f9bfe0a02ffff077a1a98065069b52744e31723.zip
llvm-0f9bfe0a02ffff077a1a98065069b52744e31723.tar.gz
llvm-0f9bfe0a02ffff077a1a98065069b52744e31723.tar.bz2
[Sanitizers][Atos] Remove null-ing of atos process pointer
Currently, when we send an address to atos to be symbolized, it is expected that atos returns with more than it was sent, i.e. symbol information for that address. In the case where only the address is returned, we currently null the pointer to the atos process. Typically, for modules where no symbolication is expected, we do not send the address to atos. However, in new simulators there is an early call that atos does not return any symbol information for. And in this case, because we have gotten rid of the pointer to the process, no subsequent frames are symbolicated, even tho atos is still working/running. This patch removes the nulling of the pointer to the process. This allows subsequent calls to atos even after an unexpected result. It also now Reports what has happened and the address this occurred. This will improve symbolication in cases where we get an unepxected result, and will make it easier to diagnose atos if it is not symbolicating as expected. Filed a radar about the change of behavior 107621524 rdar://107169715 Differential Revision: https://reviews.llvm.org/D147725
Diffstat (limited to 'llvm/docs/CommandGuide/llvm-remarkutil.rst')
0 files changed, 0 insertions, 0 deletions