Manual memory management might lead to unpredictable results
GoogleCodeExporter opened this issue · 0 comments
GoogleCodeExporter commented
I'm not 100% sure this is a Dil bug, since I only can reproduce it using a
custom GC (see http://git.llucax.com.ar/w/software/dgc/naive.git), but it
looks like it could be.
If I make the gc_free() function a NOP, all works as expected, but if not,
I get a weird help message when running Dil without arguments.
There several manually deleted object that could be the reason for such
problem. This might be related to issue 11.
Original issue reported on code.google.com by llu...@gmail.com on 6 Sep 2009 at 9:23
- Merged into: #11
GoogleCodeExporter commented
You can read the full story about how I noticed that and the debugging I made
in this
blog post: http://proj.llucax.com.ar/blog/dgc/blog/post/-11ccf34d
Original comment by llu...@gmail.com on 6 Sep 2009 at 9:25
GoogleCodeExporter commented
Original comment by aziz.koe...@gmail.com on 23 Feb 2010 at 6:58
- Changed state: Accepted
GoogleCodeExporter commented
Original comment by aziz.koe...@gmail.com on 23 Feb 2010 at 10:43
- Changed state: Duplicate
GoogleCodeExporter commented
Original comment by aziz.koe...@gmail.com on 26 Feb 2010 at 6:53