-
• #2
There's a GDB macro called
whereami
in.gdbinit
that should tell you what the call was.Looks to me like that's an issue when running
jsvCopy
on a 'bound' function parameter. Could be it's an argument type thatjsvCopy
doesn't usually get run with.If you can find out what the parameter was (
p jsvTrace(value,0)
injspeFunctionCall
's scope) it should be trivial to reproduce. -
• #3
No gdb :-). But I should be able to add the jsvTrace.
-
• #4
Ahh, yeah :) I guess an assert_with_var would be cool, and then it could trace the offending variable if the assert failed.
I'm continuing to have issues that I believe are related to using
bind()
. The call of the function returned crashes. I don't know how to repro it in a simple situation yet. I do have a stack back-trace. The assertion is in jsvRef:The lower part of the stack is (top-down):
Any clue? How can I troubleshoot this? Any way I can find out which JS statement caused this?