It seems that after installing this new update, CorTool crashes as soon as it is open now.

Same as steveirwin:
I am also having the sudden quit problem!
I try to open the application and it quits without explanation, Please help!

I need to know exactly what version of Mac you two are running.

Go to [Apple Logo Menu] -> "About This Mac" and tell me the version number.

Woah, I've just updated (forgot about pressing the button) and it's crashing for me as well.
OS 10.6.3

If anyone wants the second-to-most-recent version (non PPC), here.
http://dl.dropbox.com/u/814625/CorTool.app.zip

This is certainly strange. I can run it perfectly fine on 10.6.3

Perhaps it relies on something from the Dev Tools?
I have the base Dev stuff installed though.

Do you have the 10.4 SDK installed? It's something you have to specifically check to install in the installer.

Probably not, if it was not an obvious option.
Think that would cause it?
Maybe we need a 10.4 user to test it.
I have a 10.4 box, I could go dig it up is nobody else has one on hand.

This worked for me after I uninstalled the dev tools.

It also works for my friend running Leopard.

What could be wrong?

I'd be testing, but I've gone and dropped my laptop while debugging my 3D printer.
http://dl.dropbox.com/u/814625/macbook/CIMG2473.JPG

What was changed, code-wise, for the update?

Whoa. That's... crazy. Is that the one with Tiger on it?

Also.. the only things that changed code-wise are the change from Python-style foreach loops to C++-style "int i" loops. Oh, and I added some release and autorelease messages to clean up the memory leaks.

Could you run the program in Terminal.app and tell me what it says?

DUDE PHANTOM you Mac is sweet(exept from the breakage) how is it black? im running s,leopard on a macbook pro,can you get black macbooks? or is it an ibook

Phantom's MacBook isn't the new polycarbonate MacBook. It's the older plastic non-unibody MacBook from 2007 I think. Those came stock with Tiger. I also think it was the first MacBook to have an Intel processor.

Heh, I love going on tangents.
It's the 2008 model, came with Leopard and stuff. Bought it refurbished and then half-off, and upgraded the RAM to make it a better machine. (This is my advise for all Apple buyers, actually.)
I've already had the motherboard replaced to deal with a ports-wearing-out issue, under Applecare, but this damage was too severe to convince them it was not my fault. However, the tech I talked to was able to do a good job explaining what exactly the issue was... and how to fix it in a way that Apple would not notice (thus maintaining my warrantee).
Actually, I fixed it up with some hemostats, screwdrivers, and soldering. I just amputated the port outright, and I'll be replacing it later (just gotta order a compatible part from Mouser's catalog)

It's back in my hands either way.
The 10.4 machine I actually meant was an older (350MHZ!) G4 tower, currently being used as a server - it's buried under a pile of old junk. I guess I'll go get it out, because solving this seems pretty important.

Well, you can even use a Leopard machine to test it. I just need you to run the app from the terminal by browsing to CorTool.app/Contents/MacOS/ and typing ./CorTool

Then tell me what it says when it crashes.