Re: gdb-6.5 produces infinite backtrace on ARM

["Zarges, Olav" <Olav dot Zarges at imc-berlin dot de>]

Daniel Jacobowitz wrote:
> The error should be caught in backtrace_command now.  The finished
> output should still be printed.

Eclipse seems to read the stack via gdb/mi commands stack-info-depth and stack-list-frames and that
was what I was referring to (sorry). Please see log below. I tried to print the message with
warning(...) and return NULL instead of calling error(...) which seems to work but I don't know
about the side-effects this might involve.


[298.906]
207^done,new-thread-id="4",frame={level="0",addr="0x402c8d60",func="poll",args=[],from="/opt/crosstool/gcc-3.4.4-glibc-2.3.5-linux-2.6.12/arm-softfloat-linux-gnu/arm-softfloat-linux-gnu/lib/libc.so.6"}
[298.906] (gdb)
[298.906] 208-stack-info-depth
[298.968] &"Previous frame identical to this frame (corrupt stack?)\n"
[298.968] 208^error,msg="Previous frame identical to this frame (corrupt stack?)"
[298.968] (gdb)
[298.968] 209-stack-info-depth
[299.000] 209^done,depth="4"
[299.000] (gdb)
[299.000] 210-stack-info-depth
[299.015] 210^done,depth="4"
[299.015] (gdb)
[299.015] 211-thread-select 3
[299.031]
211^done,new-thread-id="3",frame={level="0",func="f2",args=[],file="../threads.cpp",fullname="/cygdrive/e/eclipse/ws_threads/Threads-arm/threads.cpp",line="30"},line="30",file="../threads.cpp"
[299.031] (gdb)
[299.031] 212-thread-select 4
[299.046]
212^done,new-thread-id="4",frame={level="0",addr="0x402c8d60",func="poll",args=[],from="/opt/crosstool/gcc-3.4.4-glibc-2.3.5-linux-2.6.12/arm-softfloat-linux-gnu/arm-softfloat-linux-gnu/lib/libc.so.6"}
[299.046] (gdb)
[299.046] 213-stack-list-frames 0 4
[299.140] &"Previous frame identical to this frame (corrupt stack?)\n"
[299.140] 213^error,msg="Previous frame identical to this frame (corrupt stack?)"
[299.140] (gdb)
[299.140] 214-thread-select 3
[299.156]