Hi,
Sorry to keep ranting about this, but after some additional
investigation I found several test cases in the gdb.base subdirectory
which all seem like valid tests for a remote target, yet try to interact
with the target by calling runto_main or continue without there being a
call to breakpoint() in the corresponding c file. Since connection is
never established between the host and the target, runtest will report
FAIL due to timeouts on the calls that it makes to the target, which
takes rather long time -- especially when the test case overrides my
timeout setting with a setting of its own. To me, this looks like a
problem that should occur for all target boards.
I mentioned display.exp in my previous post; here are some additional
ones from gdb.base that I think should be given the usual slew of
#ifdef usestubs
set_debug_traps();
breakpoint();
#endif
in the beginning of their main() functions:
call-ar-st.c
call-rt-st.c
call-strs.c
ending-run.c
long_long.c
sizeof.c
step-test.c
varargs.c
If the idea is approved, I'd be happy to contribute to these changes --
I just have to clear it with my boss first.
Orjan
