hi,
some time ago i wrote C++ code to save backtrace in a vector of strings.
it worked fine until one of system updates (~month ago), when it
suddenly started to show too short listening(s). i've tried example from
manual (man backtrace) to verify this, and it does not work properly
too. exam
Bartek 'BaSz' Szurgot a écrit :
> hi,
Hi,
> some time ago i wrote C++ code to save backtrace in a vector of strings.
> it worked fine until one of system updates (~month ago), when it
> suddenly started to show too short listening(s). i've tried example from
> manual (man backtrace) to verify
Aurelien Jarno wrote:
Bartek 'BaSz' Szurgot a écrit :
hi,
Hi,
some time ago i wrote C++ code to save backtrace in a vector of strings.
it worked fine until one of system updates (~month ago), when it
suddenly started to show too short listening(s). i've tried example from
manual (man backt
On Wed, Jan 13, 2010 at 01:01:27PM +0100, Bartek 'BaSz' Szurgot wrote:
> Aurelien Jarno wrote:
> >Bartek 'BaSz' Szurgot a écrit :
> >>hi,
> >
> >Hi,
> >
> >>some time ago i wrote C++ code to save backtrace in a vector of
> >>strings. it worked fine until one of system updates (~month
> >>ago), when
Pierre Habouzit wrote:
On Wed, Jan 13, 2010 at 01:01:27PM +0100, Bartek 'BaSz' Szurgot wrote:
Aurelien Jarno wrote:
Bartek 'BaSz' Szurgot a écrit :
hi,
Hi,
some time ago i wrote C++ code to save backtrace in a vector of
strings. it worked fine until one of system updates (~month
ago), when
Hello!
> 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 G
6 matches
Mail list logo