Re: Debugging a Memory Leak

2014-11-18 Thread Etienne via Digitalmars-d-learn
On 2014-11-17 6:12 PM, Maxime Chevalier-Boisvert wrote: Help or advice on solving this problem is welcome. I've tried dumping logs from the garbage collection process and it's the biggest waste of time. Even if you left a reference somewhere, the logs will not help identify the code that caus

Re: Debugging a Memory Leak

2014-11-18 Thread Steven Schveighoffer via Digitalmars-d-learn
On 11/17/14 11:41 PM, Maxime Chevalier-Boisvert wrote: GC problems are *nasty*. My advice is to run the simplest program you can think of that still exhibits the problem, and then put in printf debugging everywhere to see where it breaks down. Not sure if this is useful. Unfortunately, the pro

Re: Debugging a Memory Leak

2014-11-17 Thread Vladimir Panteleev via Digitalmars-d-learn
On Monday, 17 November 2014 at 23:12:10 UTC, Maxime Chevalier-Boisvert wrote: Help or advice on solving this problem is welcome. The D GC has some debugging code which might be a little helpful (check the commented-out debug = X lines in druntime/src/gc/gc.d). Specifically, debug=LOGGING acti

Re: Debugging a Memory Leak

2014-11-17 Thread Maxime Chevalier-Boisvert via Digitalmars-d-learn
GC problems are *nasty*. My advice is to run the simplest program you can think of that still exhibits the problem, and then put in printf debugging everywhere to see where it breaks down. Not sure if this is useful. Unfortunately, the program doesn't break or crash. It just keeps allocatin

Re: Debugging a Memory Leak

2014-11-17 Thread Steven Schveighoffer via Digitalmars-d-learn
On 11/17/14 6:12 PM, Maxime Chevalier-Boisvert wrote: There seems to be a memory leak in the Higgs compiler. This problem shows up when running our test suite (`make test` command). A new VM object is created for each unittest block, e.g.: https://github.com/maximecb/Higgs/blob/master/source/run