Mail Archives: djgpp/2004/11/02/11:01:14
boohiss <boohiss AT cubesource DOT net> wrote:
> I have written a class with my own constructor and destructor. I declare
> an object of this class globally.
> The class is constructed just fine, but when the program exits, the
> destructor is being called twice for some
> reason unknown to me. This is causing a seg fault, since I am trying to
> write to a file from a string array
> in the destructor, and the 2nd time the destructor is called, it writes
> anywhere from 80-100k of garbage to my
> file.
>
> I am *not* calling this destructor anywhere in the program, it should only
> be called once (implicitly) upon
> program end.
>
> Any idea what I'm doing wrong here?
No, because you haven't posted your code. Please post the smallest
self-contained compilable example that will duplicate the problem you
describe, so that we can copy and paste and try it out for ourselves.
(No more than 50 lines, please.)
Still, if I had to guess ... Hmmm, my crystal ball tells me that your
constructor allocates memory dynamically, that you didn't bother to
define a proper copy constructor, and somewhere in your program, the
(compiler-generated default) copy constructor is called implicitly -
presto, your destructor is called twice, and the same dynamically
allocated memory is deleted twice, which leads to a seg fault.
Solution: Define a proper copy constructor.
Or maybe not. Without your posting some code, how could we possibly
know?
Best regards,
Tom
- Raw text -