Failing GDB unit tests
Milian Wolff
mail at milianw.de
Sat Jan 14 19:25:04 UTC 2012
Hey all, esp. Niko.
Could someone with more knowledge than me look into these issues:
--- ALL FAILED TESTS ---
FAIL! : GDBDebugger::GdbTest::testVariablesWatches() '0' didn't match
expected '1' in
/home/milian/projects/kde4/kdevelop/debuggers/gdb/unittests/gdbtest.cpp:966
Loc:
[/home/milian/projects/kde4/kdevelop/debuggers/gdb/unittests/gdbtest.cpp(172)]
=> no idea what's broken here
FAIL! : GDBDebugger::GdbTest::testRemoteDebugInsertBreakpointPickupOnlyOnce()
Didn't reach state in
/home/milian/projects/kde4/kdevelop/debuggers/gdb/unittests/gdbtest.cpp:1449
Loc:
[/home/milian/projects/kde4/kdevelop/debuggers/gdb/unittests/gdbtest.cpp(1513)]
FAIL! : GDBDebugger::GdbTest::testRemoteDebugInsertBreakpointPickupOnlyOnce()
Compared values are not the same
Actual (session->line()): 0
Expected (29): 29
Loc:
[/home/milian/projects/kde4/kdevelop/debuggers/gdb/unittests/gdbtest.cpp(1451)]
=> these two fail because "shellscript" is not found, I think Niko you forgot
to add this? Furthermore QDir::currentPath()+"..." will break if the unit test
is run from a different directory (which I do all the time!), hence this
should probably use findSourceFile() instead.
Cheers
--
Milian Wolff
mail at milianw.de
http://milianw.de
More information about the KDevelop-devel
mailing list