Raúl Sánchez Siles schrieb:
Chris Liechti wrote:
1)
and the call stack isn't showing a stack. it shows the correct function
and depth, but repeats the same name on every level instead of keeping
the correct name of the calling function.
I'm not a gdb hacker, but I'll investigate this. I can't promise anything
though.
Did you get this from simulator or from gdbproxy?
sim
I wonder if you added the --disable-gdbtk configure switch and if so
wether that would be relevant. Could you try removing that switch or
specifying --enable-gdbtk. I'm not an insight user myself so I haven't
tested it.
no, neither of these options.
as Hardy pointed out some weird behavior is there since the gdb-6.0 patches.
chris
