Hi Everyone, Some of our internal users recently ran into various issues related to the new PyBind wrappers. These are the issues I'm aware of:
* Events implemented in Python aren't reference counted correctly. There are cases where the Python side of an event gets deallocated, but not the native object. The native object gets confused when the event fires. * The --debug-start and --debug-stop options broke because of API changes in Python events. * Some uses of vectors of address ranges cause out-of-range memory accesses in the Python bindings. These sometimes manifest themselves as a std::bad_alloc exception. From what we have seen, these only occur for debug builds. I have posted fixes for all of the issues above on the pybind/fixes [1] topic and a set of patches to upgrade to PyBind 2.1.1 [2]. //Andreas [1] https://gem5-review.googlesource.com/#/q/topic:pybind/fixes+(status:open+OR+status:merged) [2] https://gem5-review.googlesource.com/#/q/topic:pybind/v2.1.1+(status:open+OR+status:merged) IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
