From: Erik H. <eh...@gm...> - 2009-03-16 08:28:52
|
On Mon, Mar 16, 2009 at 1:00 AM, Don Cohen <don...@is...> wrote: > Erik Huelsmann writes: > > It looks like the issue reported by Don (and its resolution) also > > resolved a number of test cases. > > Thanks. > > Here's a question/problem related to debugging. > (defun f(x)(error "xxx")) > (f (list 1 2 3)) > now from the debugger is there some way to get the value of x? > > I'd hope to be able to just type > x > and get back the value. > But I get back an unbound variable error. That's what I'd expect, yes. Unfortunately, I have no idea how to fix this in the short term; I thought about it in the car on my way to work this morning, but there's no "easy fix": the java code compiles references to variables straight into the code, using direct memory slots. However, the Java memory protection model prevents us from accessing the memory directly. We'd need to build debugging infrastructure to allow access to variables like that. It's not impossible, but a long way to go. Sorry to have such a disappointing answer (I'm even disappointed myself!). Bye, Erik. |