Forums > MaxMSP

Error to decode ;-)

February 22, 2012 | 9:05 pm

HI all,
unfortunately I’m not yet capable of decoding errors in my system…
My Max application crashed, and i was wondering if anybody could give me some insight on how to understand where the problem is
thanks everybody

Attachments:
  1. error.rtf

February 23, 2012 | 2:18 pm

Probably triggered by a ‘refer’ message to your coll.


February 24, 2012 | 11:37 am

yep, it was a "refer thing". so i assume this line

"Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.cycling74.coll 0x183f7b84 coll_refer + 41"

are the ones which report the origin of the crash.
I didn’t dig into creashreports before. Interesting.
does anybody know what "0x183f7b84" and "+ 41" stands for?
So next time I won’t bother you on the forum ;-)

thanks!


February 24, 2012 | 11:42 am

I think you can safely forget those "0x183f7b84" and "+ 41"
if you have a reproducible crash with your patch with the latest version of max please report it to cycling
It seems that you use 5.1.7 (runtime? standalone?) it might be worth to update to 5.1.9 or the latest version of max 6, maybe your problem is already fixed in those latest versions


February 27, 2012 | 1:34 pm

mmm… this is driving me nuts. still not resolverd, and all the coll seems fine… i’ll try to install newest version of Max. Cross fingers… Thanks a lot vanille, Timo and Peter for your help!


February 27, 2012 | 2:16 pm

… and the same problems occurs with Lion, too.
here’s the new crash report. looks like we have some more info here.. like this one:
__TEXT 0000000000001000-000000000037d000 [ 3568K] r-x/rwx SM=COW
in the link vanilla posted looks like it’s a problem related to read only memory, so this could point to some more interesting understanding… cross fingers…

Attachments:
  1. lion.rtf

March 1, 2012 | 10:44 am

ok, I solved the crash, and for maxers of the future I’ll share what the problem was:
i was referring a coll which wasn’t there!
a typo had max crashing, so.
Thanks a lot everyone who helped me.

I already have another crash, different from that one, but I’ll try to decode the creashlog myself, not to stress too much… ;-)


Viewing 7 posts - 1 through 7 (of 7 total)