I wonder if there's an XY Problem here. Why do you want to find all places in the code that access the hash?
My only suggestion would be to tie the hash to something that will report on access to it. You can create a access methods that will log or otherwise output information taken from caller. Then run your test suite on it and all the points of access should jump out.
In reply to Re: Find whether code can change a module variable
by kyle
in thread Find whether code can change a module variable
by ganeshk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |