Well since this crash happens in raylib land, and is almost certainly a null
pointer dereference, and raylib is probably written in a way that calling
initWindow also initializes some other core parts of the library... Yes you
could use a debugger and go up the call stack. If you want to do that you should
compile your Nim program with the `--debugger:native` flag to get line info and
symbols.

But since the crash is happening in the C dynamic library (which maybe was or
wasn't built with debug symbols), it's a bit trickier