[Openmcl-devel] applying call-next-method and mop

Gary Byers gb at clozure.com
Fri May 5 18:22:58 UTC 2006

I'm still looking for this bug, but just to clarify something mentioned in
the README file for the x86-64 port:

On Fri, 5 May 2006, James Bielman wrote:

[From the backtrace that James sent:]

> (2AAAABA55970) : 9 (%LOAD ? T ? :ERROR :DEFAULT) 3189

Backtrace is supposed to show the current values of all required
arguments associated with the function call that created a stack frame
(it could try a little harder and try to show the values of all
supplied arguments.  That's a little heuristic, but it could often
guess mostly right.)  On x86-64, it isn't able to find the values of
arguments that were assigned to callee-save registers (mostly because
I thought that this was harder than it is.  In the call to %LOAD
above, this applies to the second and 4th arguments (which print as "?".)

More information about the Openmcl-devel mailing list