stack vs heap destruction problem

[Jamie Burns]

Hello,

I have a function which uses an object I made. The object simply parses a
text file and provides access to some of the data.

I am trying to use it in a method of a different object.

The problem is, when I declare it like this:

{
Properties properties("/tmp/data.properties");
// use object...
}

It causes a SEGFAULT when its destructor is called every time.

But if I do:

{
auto_ptr<Properties> properties(new Properties("/tmp/data.properties"));
// use object...
}

Then it destructs perfectly every time.

Is there an issue declaring things on the stack vs heap?

Why does this happen?

Jamie.

 

[Shezan Baig]

Hello,

I have a function which uses an object I made. The object simply parses a
text file and provides access to some of the data.

I am trying to use it in a method of a different object.

The problem is, when I declare it like this:

{
Properties properties("/tmp/data.properties");
// use object...
}

It causes a SEGFAULT when its destructor is called every time.

But if I do:

{
auto_ptr<Properties> properties(new Properties("/tmp/data.properties"));
// use object...
}

Then it destructs perfectly every time.

Is there an issue declaring things on the stack vs heap?

Why does this happen?

Jamie.

What does your constructor & destructor do? Pls post code.

 

[David White]

Hello,

I have a function which uses an object I made. The object simply parses a
text file and provides access to some of the data.

I am trying to use it in a method of a different object.

The problem is, when I declare it like this:

{
Properties properties("/tmp/data.properties");
// use object...

Have you tried _not_ using the object to see what happens?

}

It causes a SEGFAULT when its destructor is called every time.

But if I do:

{
auto_ptr<Properties> properties(new Properties("/tmp/data.properties"));
// use object...
}

Then it destructs perfectly every time.

Is there an issue declaring things on the stack vs heap?

No, unless you don't have enough stack or you are doing something somewhere
that depends on which you choose.

Why does this happen?

My guess is that you have a bug somewhere that, purely by accident,
manifests itself within the destructor when you use the automatic (stack)
version. Without seeing all the code being executed, that's the best I can
do.

DW