5100b81d1c
When the last event is removed from a breakpoint, then the breakpoint itself is uninstalled from IRIS, and the list is deleted. Even though the list has been traversed and so we don't lose track of any other events that need to be processed, we also still need to check against end() to see that we're done. If that now freed memory gets overwritten, then we won't see the end and will wander right off the end of the list into nonsense. This change modifies the breakpoint info tracking structure to keep a shared pointer to the event list. The pointer will still automatically manage the list's memory so that it doesn't leak, and it won't get deleted out from under us as we're iterating through it. Change-Id: I5ad0f095d07f0a3a5cce9c10f03121827a674c33 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/24965 Maintainer: Gabe Black <gabeblack@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Chun-Chen TK Hsu <chunchenhsu@google.com>
This is the gem5 simulator. The main website can be found at http://www.gem5.org A good starting point is http://www.gem5.org/about, and for more information about building the simulator and getting started please see http://www.gem5.org/documentation and http://www.gem5.org/documentation/learning_gem5/introduction. To build gem5, you will need the following software: g++ or clang, Python (gem5 links in the Python interpreter), SCons, SWIG, zlib, m4, and lastly protobuf if you want trace capture and playback support. Please see http://www.gem5.org/documentation/general_docs/building for more details concerning the minimum versions of the aforementioned tools. Once you have all dependencies resolved, type 'scons build/<ARCH>/gem5.opt' where ARCH is one of ARM, NULL, MIPS, POWER, SPARC, or X86. This will build an optimized version of the gem5 binary (gem5.opt) for the the specified architecture. See http://www.gem5.org/documentation/general_docs/building for more details and options. The basic source release includes these subdirectories: - configs: example simulation configuration scripts - ext: less-common external packages needed to build gem5 - src: source code of the gem5 simulator - system: source for some optional system software for simulated systems - tests: regression tests - util: useful utility programs and files To run full-system simulations, you will need compiled system firmware (console and PALcode for Alpha), kernel binaries and one or more disk images. If you have questions, please send mail to gem5-users@gem5.org Enjoy using gem5 and please share your modifications and extensions.