> Here is an example of a crash I just got. Recompiling the library after running something with a GUI: > > Process: SuperCollider [38410] > Path: /Users/joshp/supercollider/supercollider/build/SuperCollider.app/Contents/MacOS/SuperCollider > Identifier: net.sourceforge.supercollider > Version: ??? (-Unofficial Build-) > Code Type: X86 (Native) > Parent Process: launchd [197] > > Date/Time: 2009-12-03 22:17:41.191 -0800 > OS Version: Mac OS X 10.6.2 (10C540) > Report Version: 6 > > Interval Since Last Report: 348765 sec > Crashes Since Last Report: 4 > Per-App Interval Since Last Report: 238613 sec > Per-App Crashes Since Last Report: 1 > Anonymous UUID: DFFD0287-0CBC-4EBB-BDD0-A66E144F54CD > > Exception Type: EXC_CRASH (SIGABRT) > Exception Codes: 0x0000000000000000, 0x0000000000000000 > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Application Specific Information: > Assertion failed: (IsPtr(slot)), function slotRawPtr, file /Users/joshp/supercollider/supercollider/Headers/lang/PyrSlot32.h, line 252. this is just an assertion failure during a raw access to a slot as pointer, which doesn't contain a pointer. can you check (debug), what type is actually stored in the slot? i wonder, if null pointers are actually stored as pointer or encoded as nil or boolean values. this would raise assertions. this assertion does not have any influence on the run-time behavior of a release build, though ... it is just an additional type check ... tim -- tim@xxxxxxxxxx http://tim.klingt.org Your mind will answer most questions if you learn to relax and wait for the answer. William S. Burroughs
Attachment:
signature.asc
Description: OpenPGP digital signature