summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lldbplatformutil.py
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2017-11-07 10:36:36 +0000
committerPavel Labath <labath@google.com>2017-11-07 10:36:36 +0000
commit881fe8ecb2d3f525e8ee844fd0a083cbe91752ee (patch)
tree0f56eeab93aac8e816c5e924fd8e60841b0e7a33 /lldb/packages/Python/lldbsuite/test/lldbplatformutil.py
parentaf9814a1fcb2b6d369f30262a3e03040d66f77b7 (diff)
downloadbcm5719-llvm-881fe8ecb2d3f525e8ee844fd0a083cbe91752ee.tar.gz
bcm5719-llvm-881fe8ecb2d3f525e8ee844fd0a083cbe91752ee.zip
"Fix" concurrent events test for arm
Summary: The test incremented an atomic varible to trigger the watchpoint event. On arm64 this compiled to a ldaxr/stlxr loop, with the watchpoint being triggered in the middle of the loop. Hitting the watchpoint resets the exclusive monitor, and forces the process to loop one more time, hitting the watchpoint again, etc. While it would be nice if the debugger was able to resume from this situation, this is not trivial, and is not what this test is about. Therefore, I propose to change this to a simple store to a normal variable (which should still trip the watchpoint everywhere, but without atomic loops) and file a bug to investigate the possibilities of handling the watchpoints in atomic loops in a more reasonable way. Reviewers: clayborg Subscribers: aemerson, kristof.beyls, lldb-commits Differential Revision: https://reviews.llvm.org/D39680 llvm-svn: 317561
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbplatformutil.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud