<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
OK; I will review your emails and try to find a specific piece of code that we can run.<BR>
<BR>
I maybe able to instrument the code sufficiently for you to run it and get something valuable from it.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
On Fri, 2006-01-13 at 18:49 -0500, Waldo Rubinstein wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">Robert,</FONT><BR>
<BR>
<BR>
<FONT COLOR="#000000">I've tried to tackle this to no avail. Maybe my knowledge does not extend that far yet :(</FONT><BR>
<BR>
<BR>
<FONT COLOR="#000000">Little more help would be needed. Maybe someone else's participation could help.</FONT><BR>
<BR>
<BR>
<FONT COLOR="#000000">Thanks,</FONT><BR>
<FONT COLOR="#000000">Waldo</FONT><BR>
<BR>
<BR>
<FONT COLOR="#000000">On Jan 13, 2006, at 2:32 PM, Robert L. Read wrote:</FONT><BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">It's not clear to me that it matters.</FONT><BR>
<BR>
<FONT COLOR="#000000">Going either direction will likely lead to a solution. I would take Andrew's advice, </FONT><BR>
<FONT COLOR="#000000">since his hunch may have vailidity, and also because it is the first failure in the test suite.</FONT><BR>
<BR>
<FONT COLOR="#000000">But the course of action would be the same:</FONT><BR>
<BR>
<FONT COLOR="#000000">1) Take the test that fails, copy the code out of it into a separate file where the RT </FONT><BR>
<FONT COLOR="#000000">code won't obscure the problem.</FONT><BR>
<FONT COLOR="#000000">2) Instrument the code to find the earliest possible error; in this case, that may be </FONT><BR>
<FONT COLOR="#000000">the failure of that instantiation code to let you get to that slot, or maybe some other slot.</FONT><BR>
<FONT COLOR="#000000">3) Whenever you want, I will take your test code and run it under SBCL.</FONT><BR>
<BR>
<FONT COLOR="#000000">In this way we should be able to relatively quickly determine the important difference</FONT><BR>
<FONT COLOR="#000000">between SBCL and OpenMCL. Depending on what you find, I will likely need Andrew's</FONT><BR>
<FONT COLOR="#000000">advice on how to fix it.</FONT><BR>
<BR>
<BR>
<BR>
<FONT COLOR="#000000">On Fri, 2006-01-13 at 14:10 -0500, Waldo Rubinstein wrote: </FONT>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Thanks Andrew. Robert, how do you want to proceed. Where should I </FONT>
<FONT COLOR="#000000">look for potential CLOS problems?</FONT>
<FONT COLOR="#000000">- Waldo</FONT>
<FONT COLOR="#000000">On Jan 13, 2006, at 1:40 PM, Andrew Blumberg wrote:</FONT>
<FONT COLOR="#000000">> hi robert and waldo,</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> before going too far in debugging the secondary indices part of </FONT>
<FONT COLOR="#000000">> the problem, i think it's worth trying to figure out the CLOS </FONT>
<FONT COLOR="#000000">> problem --- i suspect that the rest of the issue might be a symptom </FONT>
<FONT COLOR="#000000">> of that, and "fixing" the secondary indices stuff might just paper </FONT>
<FONT COLOR="#000000">> over the real problem. if you're going to spend time instrumenting </FONT>
<FONT COLOR="#000000">> code, better to investigate the CLOS test failures first.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> - andrew</FONT>
</PRE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
<BR>
</BLOCKQUOTE>
</BODY>
</HTML>