After some inspection of gdb and gem5's source I found the problem. It seems as though changeset 10037 broke support for gdb in 32 bit ARM. Specifically the line:
const int MAX_NUMREGS = NUMREGS_64; I know gem5 will only support AArch64 going forward, so is this something we don't care about? I.e., should users just modify this manually if they want to use gdb with 32 bit ARM, or would a patch that fixes this be welcomed? Anthony Gutierrez http://web.eecs.umich.edu/~atgutier On Tue, Aug 19, 2014 at 1:15 PM, Anthony Gutierrez <atgut...@umich.edu> wrote: > I'm trying to use gdb to debug a simulated program remotely. I am facing > the same problem as described here: > > http://www.mail-archive.com/gem5-users%40gem5.org/msg02766.html > > I'm using the 3.3 kernel from gem5.org/Download along with the ael img. I > am using the linaro toolchain version of gdb, which is 7.71: > > http://releases.linaro.org/14.06/components/toolchain/gdb-linaro > > I was build simply by running: ./configure --target=arm-linux-gnueabi > --prefix=./build; make -j8 ; make install > > I followed the instructions on the wiki, including using the > arm-with-neon.xml file for the tdesc. I am using the latest source from the > gem5 dev repo. However, I am still experiencing the Remote 'g' packet is > too long: ... error. Has anybody experienced this recently? Seems as though > it was working a year ago. > > Anthony Gutierrez > http://web.eecs.umich.edu/~atgutier > _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
