Which destructor call is causing my program to crash?

[Marcus P S]

I have multiple instances of STL vectors of different classes in my
program, and I am getting a crash during the destructor call for one
of these objects -- the entire program executes without a problem down
to the last line in the code, and when the destructors get called, I
get a SIGABRT.

I have not been able to pinpoint which one of these destructor calls
is causing the SIGABRT. Looking at the back trace after the crash in
gdb, it is pretty clear it is inside a vector<...> destructor, but I
can't figure out for which object.

Does anyone have any suggestions how I might be able to do this?

Thanks,
Marcus

[Bart van Ingen Schenau]

Post by Marcus P S
I have multiple instances of STL vectors of different classes in my
program, and I am getting a crash during the destructor call for one
of these objects -- the entire program executes without a problem down
to the last line in the code, and when the destructors get called, I
get a SIGABRT.
I have not been able to pinpoint which one of these destructor calls
is causing the SIGABRT. Looking at the back trace after the crash in
gdb, it is pretty clear it is inside a vector<...> destructor, but I
can't figure out for which object.
Does anyone have any suggestions how I might be able to do this?

First, make a copy of the program and store that in a secure location
(unless starting all over is a reasonable option).

Then, start stripping the program down. Take parts out and check if
stripping that part out caused the error to disappear. If not, leave it
out and take the next part out.
If taking out part A causes the error to disappear, take a critical look
at it to see if you see anything suspicious. If not, put the part *back
in* and take the next part out.

When you are down to a program of less than about 100 lines, and you
still don't have a clue what causes the problem, then post the code
here with a description of the error and the input you need to give (if
any).

Post by Marcus P S
Thanks,
Marcus

Bart v Ingen Schenau

[Danny.Wang]

Post by Marcus P S
I have multiple instances of STL vectors of different classes in my
program, and I am getting a crash during the destructor call for one
of these objects -- the entire program executes without a problem down
to the last line in the code, and when the destructors get called, I
get a SIGABRT.
I have not been able to pinpoint which one of these destructor calls
is causing the SIGABRT. Looking at the back trace after the crash in
gdb, it is pretty clear it is inside a vector<...> destructor, but I
can't figure out for which object.
Does anyone have any suggestions how I might be able to do this?

{ signature and clc++m banner removed -mod }

maybe you should add some log in destructors of those different
classes.
hope it helps.

[Thomas Richter]

Post by Marcus P S
I have multiple instances of STL vectors of different classes in my
program, and I am getting a crash during the destructor call for one
of these objects -- the entire program executes without a problem down
to the last line in the code, and when the destructors get called, I
get a SIGABRT.

Try valgrind. Likely, something's screwed up already earlier.

So long,
Thomas

[Marcus P S]

Thanks for the suggestions.

I tried logging information in my custom classes, but those did not
appear to be the problem (although I could not be 100% sure).

As backtraces for my g++ compiled code were not helpful, I tried the
Intel compiler, and then the gdb backtraces were more helpful. They
indicated that the problem was the destructor for a vector<double>
object. Digging a bit more, I found that the problem was that I was
overrunning the end of the vector by a single element, and this
corrupter the stl allocator information, and caused the SIGABRT during
the destructor.

I will have to try contacting some gdb experts to see if it is
possible to set breakpoints in destructors for cases when I do not
have the Intel compiler available.

Marcus