Well, it's probably something I'm doing. It fails on both Ubuntu Linux 16.04 and Windows 10 (both amd-64). I'll do some more digging before expecting anyone else to spend time looking at it. Are there any settings one can use to e.g. find "shouldn't happen" memory overwrite problems, short of running with Valgrind or similar? Failure occurred with various of the GCs, so I have to take another look at my code.
- Hitting a SIGSEGV in the garbage collector vsajip
- Re: Hitting a SIGSEGV in the garbage collector Araq
- Re: Hitting a SIGSEGV in the garbage collector vsajip
