[Openmcl-devel] Error Running Currency Converter

mikel evins mevins at mac.com
Tue Jul 29 07:18:56 UTC 2008

On Jul 28, 2008, at 9:40 PM, Chris Van Dusen wrote:

> Hi,
> I'm going through the currency converter example, and got to the  
> point of building the application.  After hitting Enter, the Clozure  
> IDE disappears (which, even though the tutorial says, "If all goes  
> well, BUILD-APPLICATION constructs an application bundle, copies  
> 'CurrencyConverter.nib' into it, writes the application executable,  
> and quits.", I don't know that this is what was meant).
> Anyway, the CurrencyConverter.app shows up, but when I double-click  
> it "nothing happens".  I looked in Console and found the following:
> 7/28/08 8:51:14 PM [0x0-0x8a08a].com.clozure.Clozure CL[9130] Error  
> during early application initialization:
> 7/28/08 8:51:14 PM [0x0-0x8a08a].com.clozure.Clozure CL[9130] value  
> #<A Dead Mac Pointer> is not of the expected type MACPTR.
> 7/28/08 8:51:14 PM [0x0-0x8a08a].com.clozure.Clozure CL[9130] ? for  
> help
> 7/28/08 8:51:14 PM [0x0-0x8a08a].com.clozure.Clozure CL[9130] [9130]  
> OpenMCL kernel debugger:
> 7/28/08 8:51:14 PM com.apple.launchd[73]  
> ([0x0-0x8a08a].com.clozure.Clozure CL[9130]) Exited: Killed
> Googling for the error seemed to indicate that this tends to be a  
> user error.
> Is this correct?  If so, I'll go back to triple check the code and  
> the Application Builder.  If not, would anyone know where to look  
> for possible clues?

It's also possible that recent changes broke the app builder somehow.

Try running the built application from the terminal. (open a terminal  
and run the executable that is in Currency Converter,app/Contents/ 
MacOS/). If it enters the kernel debugger as the log seems to  
indicate, then you should be able to use kernel debugger command to  
generate some useful debugging information. Use the "?" command to get  
a printout of the available commands. A stack backtrace is often  
useful for figuring out how the lisp crashed into the kernel debugger.

With any luck we can figure out why it happened and fix it, whether  
it's at your end or ours.


More information about the Openmcl-devel mailing list