|
From: Dirk M. <dm...@gm...> - 2003-10-16 13:08:16
|
On Thursday 16 October 2003 14:49, Peter Seiderer wrote: > is the following problem really a valgrind problem (and maybe resolved in > the latest snapshot)? I did not read anything about it in the news section, > but had the same problem using the new gdb-6.0 > version. We know about the problem, but there is no fix yet. As we play some nasty tricks with the stack, it is "okay" that gdb feels confused. It worked before because gdb wasn't able to correctly disassemble the method in older versions. Now it can, and we cannot trick it into unwinding the stack correctly anymore. Another solution has to be found. |