On Fri, Dec 07, 2007 at 08:45:00AM +0100, Johannes Hofmann wrote:
The stack seems to be empty. With the following patch I get at least consistently:
(gdb) p top $1 = (class dw::core::Iterator *) 0x0 [snip]
OK, thanks for that. I'll try getting my head round iterators today.
PS: Compiling the whole thing with -fno-inline makes debugging much easier.
I'm already using -g -O0 as the valgrind docs recommend. Doesn't -O0 imply -fno-inline? The gcc info describes -O0 as "Do not optimize." and says under -fno-inline "Note that if you are not optimizing, no functions can be expanded inline." which suggests that -O0 makes -fno-inline redundant. I certainly noticed functions disappearing from the stack trace before I selected -O0. Regards, Jeremy Henty