Hello, Pierre-Francois, The runtime time error suggests the possibility of memory corruption. The scenario I am envisioning is the following. The get-key binding is initially correctly, but at some point in the execution flow, it is being corrupted, eventually being reported as the error you are seeing in pvt-maker:dump. I have seen similar errors before, and they were generally caused by c code that I was interfacing with; the c code erroneously overwrote memory it should not have. Do you happen to be interfacing with c as a part of your project? The memory layout of a program is sensitive to not only changes in your code (such as the addition of a print statement) but also to what optimizations are used. This could explain why the code works when data-flow is disabled or when a print statement is added. If your program does not interface with c, compiling for the JVM backend may help you diagnose the underlying issue. The runtime errors provided by the JVM backend are different and sometimes can point you in the direction of the underlying problem. It would be great if you could provide the problematic code or, even better, a small example demonstrating the issue. I know this is not always possible, but it is very hard to provide assistance without such information.
Best Regards,Joseph Donaldson
