SecurityManager: Don't use iterator after erase()
After we erase() 'entry', it is invalidated. So we cache entry->second prior to the erase() call, to avoid using 'entry' after erase. Test: TreeHugger Change-Id: Icb470cd79bbf1bfda12c2f882c3553fd33755554
Loading
Please register or sign in to comment