Am Dienstag, den 16.08.2011, 22:42 +0200 schrieb Marek Pietrzak: > Ok, I can see the point now. I was curious and exported GdbServer class > with SWIG. Looks like it works without much effort. The usage would be > roughly the following: > > sc = pysimulavr.SystemClock.Instance() > dev = pysimulavr.AvrFactory.instance().makeDevice(avrproc) > dev.SetClockFreq(62) > dev.Load(elffile) > port = 2144 > gdb = pysimulavr.GdbServer(dev,port,0) > sc.Add(gdb) > sc.Endless() > > > I was able to connect with gdb and do simple debugging though I'm not > sure how stable that is. That's 3 changed lines total if you're > interested in this change I am.
With this change, is it only possible to connect to one core of a multicore simulation (the interface supports assigning gdb-ports to devices but the implementation has some global state), or was the following statement wrong? Am Montag, den 15.08.2011, 22:34 +0200 schrieb Petr Hluzín: > You cannot simulate multiple AVR chips with GDB because our GDB > processing code does not support multiple processes and we cannot > pretend multiple GDB servers now. _______________________________________________ Simulavr-devel mailing list Simulavr-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/simulavr-devel