[PATCH] debugging: fix loader.py to handle "osv runqueue" properly

[Waldemar Kozaczuk]

Apparently existing implementation of "osv runqueue" in loader.py
navigates the sched::cpus::runqueue structure which is an rbtree
in a way that started breaking at some point probably with newer
versions of boost.

To fix it we simply use the existing intrusive_set_root_node() method
to help us navigate runqueue in a more resilient way.

Signed-off-by: Waldemar Kozaczuk <jwkoz...@gmail.com>
---
scripts/loader.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/scripts/loader.py b/scripts/loader.py
index 6270d980..c59d7e6f 100644
--- a/scripts/loader.py
+++ b/scripts/loader.py
@@ -1489,8 +1489,7 @@ def runqueue(cpuid, node=None):
cpus = gdb.lookup_global_symbol('sched::cpus').value()
cpu = cpus['_M_impl']['_M_start'][cpuid]
rq = cpu['runqueue']
- p = rq['data_']['node_plus_pred_']
- node = p['header_plus_size_']['header_']['parent_']
+ node = intrusive_set_root_node(rq)

if node:
offset = gdb.parse_and_eval('(int)&((sched::thread *)0)->_runqueue_link')
--
2.25.1

[Commit Bot]

From: Waldemar Kozaczuk <jwkoz...@gmail.com>
Committer: Waldemar Kozaczuk <jwkoz...@gmail.com>
Branch: master

debugging: fix loader.py to handle "osv runqueue" properly

Apparently existing implementation of "osv runqueue" in loader.py
navigates the sched::cpus::runqueue structure which is an rbtree
in a way that started breaking at some point probably with newer
versions of boost.

To fix it we simply use the existing intrusive_set_root_node() method
to help us navigate runqueue in a more resilient way.

Signed-off-by: Waldemar Kozaczuk <jwkoz...@gmail.com>

---

diff --git a/scripts/loader.py b/scripts/loader.py