BUG: Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.

February 25, 2006 · 1 min read

In .NET 2.0 i had a serious bug and screwed my head, for me the below code looks fine,

        try{

if (retVal == 0) Response.Redirect("Success.aspx?evt=0");

if (retVal == -2) //Email-Id is already present Response.Redirect("Success.aspx?evt=1");

if (retVal == -1) //Some error occured Response.Redirect("Success.aspx?evt=2");

} catch(Exception error) { Response.Redirect("Success.aspx?evt=2"); } finally{}

I sware there is no bug in this code, when tried to execute this code it creates an exception

Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.

I was stunned by seeing once after i commented the try catch block, it worked fine. Guys, any idea about this?

This article is part of the GWB Archives. Original Author: Vadivel Kumar

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.