+1
Completed

Defeat the Evil Optimized Away Overlord

Mike-EEE 1 year ago in New features updated 10 months ago 2

One of the truly frustrating aspects of Visual Studio debugging is encountering the "Cannot obtain value of local or argument as it is not available at this instruction pointer, possibly because it has been optimized away."

It would nothing short of awesome to see the talent there at Team Oz Code harnessed to defeat this malevolent and trickster beast of the IDE ages.

Answer

Answer
Completed

This error message is indeed really annoying, it typically appears while debugging code that was compiled with optimizations. This usually appears when debugging third party code and in production debugging scenarios.

We have a new product coming out soon, which is designed for third party code and in production debugging scenarios. The new product will solve this exact problem and allow you to view local variables even if they were optimized away. 

It's currently in a beta phase, to read more and sign up visit our website

BAD, I'M UNSATISFIED

Hey all... I totally misunderstood your product here, apologies. I thought it was the next version of OzCode, but it is a totally new product altogether, one that costs TWENTY-FIVE TIMES what the personal license costs currently for OzCode Personal.

Consider that the feature request here was made in the OzCode feedback forum, not for another product. Let alone one that has such a significant price differential.

As it stands, it would seem that you have replaced one overlord with another... the dreaded Steep Price Overlord. 😞 This is one to be avoided, especially in the context of open-source software development, where pennies are a challenge to procure.

Any reconsideration towards your strategy for this feature would be greatly appreciated.

Satisfaction mark by Mike-EEE 10 months ago
Answer
Completed

This error message is indeed really annoying, it typically appears while debugging code that was compiled with optimizations. This usually appears when debugging third party code and in production debugging scenarios.

We have a new product coming out soon, which is designed for third party code and in production debugging scenarios. The new product will solve this exact problem and allow you to view local variables even if they were optimized away. 

It's currently in a beta phase, to read more and sign up visit our website

Hey all... I totally misunderstood your product here, apologies. I thought it was the next version of OzCode, but it is a totally new product altogether, one that costs TWENTY-FIVE TIMES what the personal license costs currently for OzCode Personal.

Consider that the feature request here was made in the OzCode feedback forum, not for another product. Let alone one that has such a significant price differential.

As it stands, it would seem that you have replaced one overlord with another... the dreaded Steep Price Overlord. 😞 This is one to be avoided, especially in the context of open-source software development, where pennies are a challenge to procure.

Any reconsideration towards your strategy for this feature would be greatly appreciated.