gdb: make inferior_list use intrusive_list
Change inferior_list, the global list of inferiors, to use intrusive_list. I think most other changes are somewhat obvious fallouts from this change. There is a small change in behavior in scoped_mock_context. Before this patch, constructing a scoped_mock_context would replace the whole inferior list with only the new mock inferior. Tests using two scoped_mock_contexts therefore needed to manually link the two inferiors together, as the second scoped_mock_context would bump the first mock inferior from the thread list. With this patch, a scoped_mock_context adds its mock inferior to the inferior list on construction, and removes it on destruction. This means that tests run with mock inferiors in the inferior list in addition to any pre-existing inferiors (there is always at least one). There is no possible pid clash problem, since each scoped mock inferior uses its own process target, and pids are per process target. Co-Authored-By: Simon Marchi <simon.marchi@efficios.com> Change-Id: I7eb6a8f867d4dcf8b8cd2dcffd118f7270756018
This commit is contained in:
parent
bf80931081
commit
08bdefb58b
10 changed files with 104 additions and 117 deletions
|
@ -2038,7 +2038,6 @@ regcache_thread_ptid_changed ()
|
|||
/* Prepare two targets with one thread each, with the same ptid. */
|
||||
scoped_mock_context<test_target_ops> target1 (arch);
|
||||
scoped_mock_context<test_target_ops> target2 (arch);
|
||||
target2.mock_inferior.next = &target1.mock_inferior;
|
||||
|
||||
ptid_t old_ptid (111, 222);
|
||||
ptid_t new_ptid (111, 333);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue