Since the latest update to Goland (2018.3.4) I'm finding that break points don't work after a panic. Anyone else seeing this?
For more context I have a number of go routines in a pipeline that I'm running tests (using go testing framework) on the output of the pipeline. I'm using break points typically on the last go routine in the chain. If my program has an error that causes a panic or slice out of bounds or other go 'crash' then I find that when I tried to run the test with debug again the breakpoint that fired before no longer fires. Exiting and restarting go land resolves.