Alright, thanks. I have a couple of leads on what happened, but since the implementation details are private I'm unsure of the best troubleshooting technique in this context.
For now I am making a minimal C project that builds a shared library and follows the same allocation pattern and FFI use.
I noticed that switching "_pointer" back to a tagged pointer type makes the program raise an error, but I suspect that's due to a tag being missing from the (malloc) call.
Once I learn my mistake I will share it here.
~slg
-------- Original Message --------
On Oct 23, 2019, 10:58 AM, Sam Tobin-Hochstadt <
sa...@cs.indiana.edu> wrote:
`#<variable-code>` is how a representation of one of the internal AST
types for the compiler is printed. When you see it, it definitely
means some memory got corrupted.
Sam
> --
> You received this message because you are subscribed to the Google Groups "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/kOdM__5k_2CVKSt5cmEUjb8Ci-00MtOsPUnBvetk5puetw-rGEyH95lFrYNQ-rgKdEOJQ7eo7boVEz9ua4RHPeUb1O9OdzsDdkQjwhuM9pA%3D%40sagegerard.com.