I’d like to automatically run submission code in Valgrind to verify correct memory management.

Submitted by Chiel de Roest on 1 December 2013 at 12:48

Using valgrind is not possible at this moment, as the weblab backend transforms c-code to Javascript (C-code -> LLVM bitcode -> Javascript) using CLang and emscripten. This is primarily done for security reasons. I don’t expect C-code to be executed on the backend of weblab shortly.

But I came across this post about emscripten. Maybe using the CORRUPTION_CHECK and other emscription compilation settings may already bring us more useful output.