l Jennings
Sent: Tuesday, February 01, 2011 12:51 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Disabling optimized methods
Alright, we're using DebugMode = true already (when the application starts with
the debugger attached) so we must be seeing something else that is causing us
ry 01, 2011 12:51 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Disabling optimized methods
Alright, we’re using DebugMode = true already (when the application starts with
the debugger attached) so we must be seeing something else that is causing us
to get the ‘function has been opti
rom: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Dino Viehland
Sent: Tuesday, February 01, 2011 12:50 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Disabling optimized methods
You can use -X:Debug now to specifiy this at the command line. If you want to
do
ilto:users-boun...@lists.ironpython.com] On Behalf Of Dino Viehland
Sent: Tuesday, February 01, 2011 12:50 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Disabling optimized methods
You can use -X:Debug now to specifiy this at the command line. If you want to
do it while you're hosting you can set
You can use -X:Debug now to specifiy this at the command line. If you want to
do it while you're hosting you can set the DebugMode option to true on the
ScriptRuntimeSetup object used to create the ScriptRuntime. You'll need to
make sure the ScriptSource's you create have filenames though.
Fr
This isn't actually optimization but rather dynamic methods. You can use the
-X:StaticMethods which will force all methods into types. But the consequence
of this is if methods are getting dynamically defined (e.g. exex "def foo():
pass") then we'll leak memory because the methods can never be
