[remote testsuite] Spurious failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro GDB |
Fix Released
|
Low
|
Ulrich Weigand |
Bug Description
Some tests cases result in FAILs when running the testsuite remotely, because of bugs in the test case. These include:
gdb.stabs/
* Hard-codes "run" instead of starting execution in a compatible manner
gdb.base/
gdb.base/
gdb.base/
* Attempt to run to entry point even though in remote mode, we already start out there
gdb.cp/
* Attempts to verify inferior stdout, even though this is not supported remotely
gdb.base/
gdb.threads/
gdb.threads/
* Require fork/exec catchpoints, which are not supported remotely
gdb.mi/
* Relies on address space randomization being disabled, which is not supported by gdbserver
These need to be fixed where (easily) possible, or else the test needs to be skipped when running remotely.
Related branches
Changed in gdb-linaro: | |
assignee: | nobody → Ulrich Weigand (uweigand) |
Changed in gdb-linaro: | |
status: | Fix Committed → Fix Released |
Some updates from current mainline.
gdb.stabs/ gdb11479. exp break-entry. exp: running to *0x8150 in runto exception. exp: continue to second throw execl.exp fork-child- threads. exp
gdb.base/
gdb.cp/
gdb.threads/
gdb.threads/
* These have all been fixed (mostly by disabling them for remote testsuite runs):
gdb.mi/ mi-var- cmd.exp: in-and- out-of- scope: in scope now
* This is actually Bug #804408
gdb.base/ nostdlib. exp: stop at run nostdlib. exp: continue to marker watch-vfork. exp: Watchpoint triggers after vfork (sw)
gdb.base/
* This test also ought to be disabled
gdb.base/
* This ought to be disabled until Bug #804407 is fixed