j
k
j a
j l
On 14 Jun 2014, at 15:23, Rasmus Malver wrote:
Yup, it's Onigmo.dylib […]
Turns out to be a stack overflow, onigmo was just where the stack pointer was when the stack guard was triggered.
Next build should fix this.
Back to the thread
Back to the list
