Ah, I see. If I go back to an old version of fhost.py, the error you're seeing is just a big hardcoded string. So there is a deliberate handler, made to look like a crash. Strange.
def notfound(e):
return u"""<pre>Process {0} stopped
* thread #1: tid = {0}, {1:#018x}, name = '{2}'
frame #0:
Process {0} stopped
* thread #8: tid = {0}, {3:#018x}
fhost`get(path='{4}') + 27 at fhost.c:139, name = 'fhost/responder', stop reason = inv...
https://0x0.st/-L59.txt