Note: - numad is "only" in universe in all releases - nothing depends on it - it is on 0.5+20150602-5 which seems rather old - But upstream commits [1] since 2015 are minimal
TL;DR no (somewhat dead) upstream fix for that available to cherry-pick Hmm, the above might have been a red herring. I get 24 bytes size even in cases where the initial value was null. Maybe the pure size of the set_p isn't waht matters. In any case lets do a non-optimized build to get around debugging issues like: (gdb) p node[node_id].cpu_list_pnode[node_id].cpu_list_p->bytes value has been optimized out Also I realized that this is a static var not only to be local but in the common sense to keep content across function calls. So initializing on init will be wrong :-) [1] https://pagure.io/numad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832915 Title: numad crashes while running kvm guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1832915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
