Comment by willvarfar
5 months ago
When you run the Fil-C versions of your favourite software, does it have a sanitizer mode that reports bugs like missing free() etc? And have you found any bugs this way?
5 months ago
When you run the Fil-C versions of your favourite software, does it have a sanitizer mode that reports bugs like missing free() etc? And have you found any bugs this way?
Well missing free is just swallowed by the GC - the leak gets fixed without any message.
I have found bugs in the software that I’ve ported, yeah.
This is neat work. I noticed on your software page some patches you had to make to get those things to compile. Have you sent those upstream? Eg, I noticed a simple 1 line bash change for example.
To add on top of this: This is a tracing GC. It only ever visits the live data, not the dead data. In other words, it would need a lot more special support if it wanted to report the dead objects.
A non-moving GC must visit dead objects.
4 replies →
Really? How does a non-moving GC make dead objects available for reallocation without visiting them?
17 replies →