On Wed, Jul 31, 2013 at 12:32 PM, David Jeske <[email protected]> wrote:
> On Wed, Jul 31, 2013 at 11:50 AM, Jonathan S. Shapiro <[email protected]>wrote: > >> You are assuming that the box containing the independent pointer is in >>> fact independent. Because of the introspection and concurrency features of >>> CLR, this assumption is wrong *in the CLR*. >>> >> > I'm curious how this is true. Are we talking about normal CLR libraries? > (I'm not thinking of the debugger interface, since that's non-standard, > not safe, and a totally different ball of wax) > It doesn't matter what kinds of code we are talking about. A correct optimizer, whether it runs at static compile time or at run time, is constrained by what *may* be done given the semantics of the runtime system. It is not entitled to assume that the code is well behaved beyond the guarantees that are enforced by the intermediate form. > I see the > StackFrame<http://msdn.microsoft.com/en-us/library/System.Diagnostics.StackFrame.aspx> > class > in System.Diagnostics, but I don't see any way to access locals. Is there a > way to see and modify another stack's locals or registers from within the > CLR? How? > I'd have to dig in to that, and it's not a priority at the moment. I'm actually uncertain what the introspection stuff exposes. We *do* know that debuggers can get to this information, from which I infer that there exists a way to do it. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
