关闭.net JIT编译器优化 [英] Switching off the .net JIT compiler optimisations

查看:101
本文介绍了关闭.net JIT编译器优化的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我们远程某个方法(使用泛型)时,远程接收器似乎无法从其他相同的命名方法中发现我们的方法。使用附加的.net源代码进行调试我已经将它放在 MethodInfo.MakeGenericMethod 调用的位置。但是,由于jit的优化,我无法查看周围的任何数据。

When we remote a method (that is using generics) the remoting sink cannot seem to discover our method from the other identical named ones. Debugging with .net source code attached I've got it to where there is a MethodInfo.MakeGenericMethod call. However I cannot look at any of the surrounding data as its been jit optimised.

几周前,我遇到了一个注册表设置,该设置将禁用此设置(特别是提到它有助于调试源代码)。但是,由于身为墙壁,我已经失去了使用它的能力,无法再次找到它。

I couple of weeks ago I came across a registry setting that would disable this setting (it specifically mentioned that it aid debugging with the source). However being a wally I've lost what I did with it and am having trouble finding it again.

推荐答案

我没有了解注册表解决方案,但是您可以使用INI文件来禁用JIT优化。

I don't know about a registry solution, but you can use an INI file to disable JIT optimazation.

简短版本是使用以下内容创建一个.ini文件(即myapp.ini)。

The short version is create an .ini file (i.e. myapp.ini) with the following contents.

[.NET Framework Debugging Control]
GenerateTrackingInfo=1
AllowOptimize=0

此处完整说明

这篇关于关闭.net JIT编译器优化的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆