Closed dogtopus closed 10 years ago
I think you have two options to prevent the SIGSEGV:
git revert 7f4e58fd6ea548983b9d2fd3aaa797784011bef3
So the problem is related to MRI 2.0's GC? Interesting... I think you can post a commit that let the program memcpy() the data when MRI 2.0 is used for compiling. (currently debian sid doesn't have 2.1 in its repository, most distribution may not have it either) Anyway, thanks for your help
So the problem is related to MRI 2.0's GC? Interesting...
Yeah, I think it wrongfully swipes the ruby values on my C stack. Not sure though, I'm not a Ruby expert =)
I think you can post a commit that let the program memcpy() the data when MRI 2.0 is used for compiling. (currently debian sid doesn't have 2.1 in its repository, most distribution may not have it either)
I'll think about it.
Anyway, thanks for your help
No problem. Are you able to execute scripts now?
Are you able to execute scripts now?
Of course :D Now it can run the default empty project perfectly
Great =)
The first script can be successfully read, but when it tries to read the next one, it has 2 situations (both not good):
Thus, the program only executes the script that on the top of the script pack and quits immediately (w/ or w/o SIGSEGV)
The script pack can be read successfully by the following programs:
also, a simple test was done using MRI 2.0's irb...