> i wondered how will original program (with tail-recursion) look
> under debugger. it looks strange, since gdb's stack and one returned
> by backtrace() differ. :/

GDB puts a lot of effort into parsing DWARF unwind tables etc. to
reconstruct the ``source code's program flow'' even after GCC's
optimizations.  glibc's backtrace function does not do that.


Attachment: signature.asc
Description: Digital signature

Reply via email to