I'm able to reproduce this issue on v5.5. I don't see it in older v5 versions so it must be something fairly new. The issue does not exist on CCSv6 beta builds.
[quote user="Jaspreet Kaur Bhambra"]Hope its not something to do with Memory allocation.[/quote]
No, the issue was that the debugger failed to read the PC at that time. But I can read it afterwards. It could be that the error will have no impact to your debug session.
CCSv6 will be released sometime next week or so. You can move to that if it is a concern.
ki