[remote testsuite] Thread support
Bug #804401 reported by
Ulrich Weigand
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linaro GDB |
Fix Released
|
Low
|
Ulrich Weigand | ||
Bug Description
Several thread-related tests are currently disabled remotely, even though it is not clear why this has to be the case. These include:
gdb.threads/
gdb.mi/
gdb.mi/
gdb.mi/gdb669.exp
* Fully disabled
gdb.threads/
gdb.threads/
* Some tests skipped
Needs some more investigation.
Related branches
| Changed in gdb-linaro: | |
| assignee: | nobody → Ulrich Weigand (uweigand) |
Revision history for this message
| Ulrich Weigand (uweigand) wrote | #1 |
| Changed in gdb-linaro: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
Revision history for this message
| Ulrich Weigand (uweigand) wrote | #2 |
| Changed in gdb-linaro: | |
| status: | Confirmed → Fix Committed |
| milestone: | none → 7.3-2011.08 |
| Changed in gdb-linaro: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It turns out that this set of tests:
gdb.threads/
gdb.mi/
gdb.mi/
gdb.mi/gdb669.exp
just works when enabled on remote targets, so we probably just ought to do that.
The second set of tests:
gdb.threads/
gdb.threads/
reflects an actual difference in behavior between GDB and gdbserver, so that seems OK.