Master's student at Concordia. Backend developer at AdGear
Erlang Debug VMs: Debugging code that crashes BEAM
When writing Erlang software, you sometimes have to write NIFs or linked-in drivers. This is a scary proposition, since debugging C code that's running in the Erlang VM is difficult, and because a faulty NIF or linked-in driver can cause an entire VM to crash! Fortunately, it's possible to debug NIFs and linked-in drivers running within BEAM with GDB and Valgrind.
Bring attention to the dangers of writing NIFs and linked-in drivers, show how to build and use Erlang's debug VMs to debug NIFs and linked-in drivers, and demonstrate the debugging of faulty C code using Erlang debug VMs.
Developers interested in writing/debugging NIFs and linked-in drivers.
By day, Richard Kallos writes code for AdGear. By night, he works towards his course-based Master's degree in Computer Science. Richard's professional career started in the summer of 2016, where he was hired as an intern at AdGear to work on optimizing an in-house compiler. Now he continues to work at AdGear as a member of the backend team surrounded by brilliant and supportive coworkers.Twitter: