[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: backtrace and demangling symbols at runtime
From: |
address@hidden |
Subject: |
Re: backtrace and demangling symbols at runtime |
Date: |
12 May 2006 01:05:58 -0700 |
User-agent: |
G2/0.2 |
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.