0 0 1 Your code is buggy and you are waiting in the office hours queue. Type 'n' to keep waiting or 's' to run valgrind.
1 1 2 You find and fix a memory allocation error. Type 'n' to keep waiting or 's' to run gdb.
2 2 3 You fix a seg fault caused by an out-of-bounds array index. Type 'n' to keep waiting or 's' to run gdb again.
3 3 4 You notice you forgot to multiply by sizeof(struct room) in a call to malloc and replace it with a call to calloc. Type 'n' to keep waiting or 's' to run valgrind.
4 4 5 You find an uninitialized variable. Type 'n' to keep waiting or 's' to run valgrind.
5 5 6 Your code passes all valgrind tests but there is still an annoying test case you can't figure out. Type 'n' to keep waiting or 's' to check discord.
6 6 7 Somebody else had the same problem you had and suggested checking for null characters. Type 'n' to keep waiting or 's' to use gdb to look for null characters.
7 7 7 It wasn't a null character but while poking around in gdb you found a function call with the wrong argument. Now everything works! Type 'q' to quit.