Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
The debugger should support moving the instruction pointer within the current method
I spoke to Zoltan about this on last xummit and he said it should be possible to implement without too much work.
Its pretty easy to implement it, its just hard to implement it in a way that doesn't make the app crash. I.e. for this code:
object o = new object ();
the JIT might not generate code to null initialize 'o', so if the initialization statement is skipped using this functionality, 'o' might contain garbage leading to a hard crash. Same for an exception handler which expects the exception to be in a stack location saved at the beginning of the code generated for the catch clause. Also, finally statements are implemented in a strange way inside the JIT, so if the user moves the ip inside a finally statement, or out of it, things will crash also.
All of this can probably be fixed, but it would be a lot of work, it would be hard to test, and it would bloat the code generated in debug mode.
Is there any easy way for JIT to detect IP move is unsafe ?
What about always initializing the references when running in the debugger?
this is implemented now