diff options
| author | Jonathan Peyton <jonathan.l.peyton@intel.com> | 2016-05-12 21:54:30 +0000 |
|---|---|---|
| committer | Jonathan Peyton <jonathan.l.peyton@intel.com> | 2016-05-12 21:54:30 +0000 |
| commit | 2b749b33ccd6f93e0d05fa5fa8afc8096c6d3de2 (patch) | |
| tree | 28e00973d85501fcd24121083870b48fb104ee0a /lldb/packages/Python/lldbsuite/test/python_api/thread | |
| parent | 01f16364084af96b11c7da8337f5c30b71d1f916 (diff) | |
| download | bcm5719-llvm-2b749b33ccd6f93e0d05fa5fa8afc8096c6d3de2.tar.gz bcm5719-llvm-2b749b33ccd6f93e0d05fa5fa8afc8096c6d3de2.zip | |
Fix team reuse with foreign threads
After hot teams were enabled by default, the library started using levels kept
in the team structure. The levels are broken in case foreign thread exits and
puts its team into the pool which is then re-used by another foreign thread.
The broken behavior observed is when printing the levels for each new team, one
gets 1, 2, 1, 2, 1, 2, etc. This makes the library believe that every other
team is nested which is incorrect. What is wanted is for the levels to be
1, 1, 1, etc.
Differential Revision: http://reviews.llvm.org/D19980
llvm-svn: 269363
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread')
0 files changed, 0 insertions, 0 deletions
