diff options
| author | Curtis Dunham <Curtis.Dunham@arm.com> | 2014-12-23 11:51:40 -0600 |
|---|---|---|
| committer | Curtis Dunham <Curtis.Dunham@arm.com> | 2014-12-23 11:51:40 -0600 |
| commit | 10b5e5431d004fe51df30140f20346b2c91248fb (patch) | |
| tree | abff13d4c9e7cbcabdf2c5533066fb957fcdfead /src/python/swig/event.i | |
| parent | 10c69bb1684c515d683a084b40ab19e5e7ee8c11 (diff) | |
| download | gem5-10b5e5431d004fe51df30140f20346b2c91248fb.tar.xz | |
sim: fix reference counting of PythonEvent
When gem5 is a slave to another simulator and the Python is only used
to initialize the configuration (and not perform actual simulation), a
"debug start" (--debug-start) event will get freed during or immediately
after the initial Python frame's execution rather than remaining in the
event queue. This tricky patch fixes the GC issue causing this.
Diffstat (limited to 'src/python/swig/event.i')
| -rw-r--r-- | src/python/swig/event.i | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/python/swig/event.i b/src/python/swig/event.i index 23bb31364..cc72794ed 100644 --- a/src/python/swig/event.i +++ b/src/python/swig/event.i @@ -71,6 +71,10 @@ } } +%typemap(out) PythonEvent* { + result->object = $result = SWIG_NewPointerObj(SWIG_as_voidptr(result), SWIGTYPE_p_PythonEvent, SWIG_POINTER_NEW); +} + %ignore EventQueue::schedule; %ignore EventQueue::deschedule; |