[IronPython] 'Cannot evaluate expression because the code of the current method is optimized.' when debugging IronPython 2.6

[Jeff Hardy]

Hmm, this is only an issue when using
System.Diagnostics.Debugger.Break(); as soon as I hit F10 all of the
variables become available.

- Jeff

On Sun, Jan 31, 2010 at 3:11 PM, Jeff Hardy <jdhardy at gmail.com> wrote:
> Hi,
> When debugging Python code with Visual Studio, I'm getting 'Cannot
> evaluate expression because the code of the current method is
> optimized.' for just about everything when trying to inspect Python
> objects, even when running with -X:Debug. This is with IronPython 2.6.
>
> I remember this working at some point in the past, so I'm wondering if
> there is something else I need to do (like a different -X: switch) to
> be able to view the values on those objects.
>
> - Jeff
>