Ok, so I ran into the same issue today, and none of the answers here seemed to work. However, there should be a very easy solution to this problem.
Instead of trying to see the values during the exception, can't you just add a breakpoint slightly before when the exception occurs? This way, your variable values should still be correct and viewable.
The only time this wouldn't work is when the exception occurs when changing the value that you want to view, but this in this case:
The variable change is bases off of other variables that you CAN view just before the exception occurrence.
The variable does not change based on any other factors except randomisers, magic numbers, etc. and should be easy to debug on itself.
There is a scenario where I haven't thought of and there actually is a problem (although very unlikely).