Open martijnbastiaan opened 5 years ago
@martijnbastiaan Is there any reproducible test case for this?
I think this might still happen if Clash throws an error
instead of ClashException
? Maybe you could try adding an error call somewhere. If we can't reproduce it I guess we can close this issue and tag it with 'non-reproducable'.
handleClashException should catch the exceptions.
To try to reproduce the error, I changed the blackbox for blockram to bogusly use its HasCallStack
argument, but handleClashException
picked it up correctly.
Hence I'm moving this to 1.4
Every once in a while a Clash bug rears its head telling user to file a bug at the Haskell bug tracker. For example:
We should never redirect users to the Haskell bug tracker. Because we can't feasibly foresee when this message will be reported, we should simply filter our output and replace it with a less offensive message.