try/except leads to infinite loop with growing memory usage about micropython HOT 7 CLOSED

There is currently no memory manager (no garbage collection) for the unix version, so that's why it eats memory. But it's certainly a bug that it runs an infinite loop.

from micropython.

Added proper nested exception handling, and basic exception type matching. Above code should now work.

from micropython.

Thanks for quick response, hope it doesn't steal cycles from hardware hacking ;-). (Though this particular issue is important enough, so I really appreciate looking into it).

Well, exception-throwing path now works (including on x86/32bit, will submit patch once cleaned up), but exception-free path leads to:

a = {1:2}
try:
    a[1]
except KeyError:
    print("caught")

./py exc.py 
py: ../py/vm.c:308: mp_execute_byte_code_2: Assertion `0' failed.
Aborted

Corresponding opcode doesn't appear to be implemented.

from micropython.

Yep, it's not fully implemented. Micro Python doesn't use reference counting (like CPython) so the action of push/pop blocks in the interpreter is a bit simpler for Micro Python. Thus, the byte code POP_BLOCK is probably only needed when exiting an exception handling block.

from micropython.

Okay, it should now work. There will still be issues with "finally" and "with" blocks.

from micropython.

Yes, confirmed working. Let's close and track finally/with somewhere else then. (Note that I didn't try to find which Python features don't work, just read that "It works only for 64-bit machines due to a small piece of x86-64 assembler for
the exception handling.", so after building for x86, I proceeded to test exactly exception handling ;-) ).

from micropython.

By "exception handling" I actually meant the underlying C exception handling that I'm using (nlr_jump). You don't see it, but it's working when you get a Python error, eg at the command line just type "foo" and it'll give you a NameError. That's using nlr_jump, written in assembler.

from micropython.