OOo and gdb/valgrind

I’ve updated the gdb testcases for OOo/c++ debugging at http://people.redhat.com/caolanm/mygdbproblems.tar.gz. Now with gdb in FC3 only one of the tests fails. I’m not convinced that breakpoints in ctor’s are fixed, but it works in the test case, so perhaps it is :-) . Deferred breakpoints on class member names works, as does repeated execution of a debugged process when deferred breakpoints have been resolved in a previous pass.

MHU has taken on a proper fix for the commandline parsing issue that confuses OOo when run from inside [val|call]grind which I was hacking around with http://people.redhat.com/caolanm/callgrind/

Meanwhile, gtkfpicker2 and ineturl1 languish in Ready for QA.

Leave a Reply