31bab6f6ac097d13fc2101bef5e6c4b2ee481e23
This test expects to load a symbol file using the load method of gem5's SymbolTable class, and then to search through it for a given symbol or address. Unfortunately, the type of file it expects to load has a format where each line is of the form: 0x00000000, symbol_name where the numerical part is the address of the symbol, and the part after the comma is the symbol name. I have not been able to find any tool which outputs a symbol file in this format, or any tool for inspecting an existing object file which will output symbols in this format. I looked at objdump, objcopy, nm, and the map file format output by gnu's linker. nm has 3 different output formats, none of which match. Usually when working with ELF files, one would just generate a new ELF file which only had debugging information like the symbol table, and then strip the symbols out of the original. Since this file format seems to have been invented from thin air, there isn't really a good way to generate a canonical file to test the loading code against, nor is being able to load this obscure format likely to be useful to anybody. If someone *did* want to load an external symbol table, they would use the ELF loader and not this. This CL deletes both this test, and the loading code in SymbolTable. Change-Id: I20402e3f35e54d1e186a92d9c83d1c06ec86bf7d Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/40620 Reviewed-by: Daniel Carvalho <odanrc@yahoo.com.br> Maintainer: Bobby R. Bruce <bbruce@ucdavis.edu> Tested-by: kokoro <noreply+kokoro@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.
Description