In case of issues like #1217, we get a very short log trace like the below:

$ nmodl invalid_name.mod
libc++abi: terminating due to uncaught exception of type std::runtime_error: NMODL Parser Error : syntax error, unexpected ., expecting NAME [Location : 6.11]
    LOCAL _kf
----------^

[1]    40873 abort      nmodl invalid_name.mod

With this change, we can run with --verbose trace to get more information what went wrong:

$ nmodl --verbose trace invalid_name.mod

See trace.log for the full output of the parser.

Of course, --verbose trace will also work if we have a valid file as well.

Some implementation notes:

• I would've added the logs directly to the logger class, but unfortunately spdlog removed the ability to use streams a while back, while Bison requires exactly a stream-like object to dump its logs. Option 2 was rewriting our own logger to add the stream there, but this would require changing all calls to logger->[LEVEL] throughout the codebase because our custom wrapper class isn't actually used, so I opted for adding it to the driver instead to keep things simple
• initially I wanted to add logs for Flex as well, but it turns out that it stubbornly dumps everything to std::cerr. I tried to work my way around it, but ended up with segfaults due to a race condition, so I'm leaving that part out for now