There is only one reason for a child class constructor to call the destructor of its base class: failure.
So, your problem is likely due to an exception that is thrown somewhere in the construction of the child. This causes the stack to be unwound and all objects are destructed which have already been constructed. Since it is the constructor of the child class that calls the constructors of all its parents, it is also the constructor of the child that calls its destructor during exception cleanup.
However, don't give too much weight to the source code line that is produced by gdb, it may be wrong. So the bug may still be something wildly different.