Syslog frees memory??

Michael Wieher michael.wieher@gmail.com
Fri May 23 16:48:00 GMT 2008


Ok, so I've been struggling with a strange issue and a broken destructor.

btw, anyone know a single-word for the idea "situations so complex
they cannot be reproduced"

Here is situation:
---------------------------
class {
   datax ** y;
   data * b;
   int numbofY;
}

destructor:
   free all in y (via for-loop & numbofY)

causes seg-fault unless i syslog something in there

however

destructor:
   free all in y(same)
   freee b

works OK

any idea why syslog makes this failure to free(b) acceptable during
execution/exit of program?



More information about the Gcc-help mailing list