Bernd Strieder napísal(a): > Probably due to inlining. You have all the code in one compilation unit. > If a constructor only calls another constructor, only that call might > be left after inlining. There are other optimization techniques with a > great influence on the call stack, e.g. tail call optimization, and I > don't know how well backtrace does with all of it. In my experience > even gdb can produce quite confusing displays on optimized code, > although it probably has better chances to get reasonable results. > > Try compiling with -O0, or try different compilation units, or add code > to print messages. >
I don't have any optimization on, but I tried with -O0 anyway, I also moved class B to another compilation unit and added some std::cout stuff to B's constructor. Yet the backtrace remains the same. _______________________________________________ help-gplusplus mailing list help-gplusplus@gnu.org http://lists.gnu.org/mailman/listinfo/help-gplusplus
