You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Gordon
Usually when there's an assertion it does a full trace, starting from
global(execInfo.root)... Not sure why it isn't doing it on ESP8266? It might help you track down what the var actually was.I'm not sure why the trace you have isn't giving any names though - it seems pretty messed up.
Since it's called from jspeFactor it's presumably in JS code, so you could find out where you are by typing
jslPrintTokenLineMarker(jsiConsolePrintString, 0, lex, lex->tokenStart, 0)By guess is that somewhere, some code is locking a variable and then not unlocking it.
The assertion could be anywhere that the variable is used (not the code actually causing the problem), because obviously the number of locks just ticks up over time, and then it just gets to the point where any subsequent lock of that var will fail.
Still, tracking down which variable it was will mean you can start to look through the bits of code that access that variable, and hopefully at some point you'll find out what isn't unlocking.
How did you get the stack trace? Is that something you did in code on the ESP8266 itself? Seems like it'd be a really handy debug tool