On Fri, 2012-05-11 at 14:20 +0100, Jeremy Bennett wrote: > On Fri, 2012-05-11 at 13:50 +0200, Peter Gavin wrote: > > On Fri, May 11, 2012 at 1:45 PM, Julius Baxter <[email protected]> > > wrote: > > > I'm not sure if I drew your attention to it a while back but I got gdb > > > sim to about the same stage (could run helloworld.) > > > > > > https://github.com/juliusbaxter/binutils-or1k/tree/gdb-sim-addon/sim > > > > > > (it was on a different branch.) > > > > > > I never got useful tracing out of it, though. I just got the result, > > > essentially. > > > > Oh, I didn't realize you had done that. Does it print using a > > syscall, or with the nop hack? > > > > > I'm not sure we need one to help verify the newlib-based toolc hain. > > > > Yeah, I don't think so either. But it would be really nice to be able > > to debug a simulated linux kernel using it :) > > Hi Pete, > > Saw your post on the CGEN mailing list. It's not really what CGEN > simulators are intended for - they are CPU simulators. Mostly they > support the newlib tool chain using callbacks to the host system for > system call support. > > Which doesn't mean it isn't an interesting exercise - I've never seen a > report of Linux running on a CGEN simulator. > > If you want to model a whole system, you need Or1ksim for (or one of the > other system simulators like QEMU). We did the regression testing of the > or32-linux- toolchain using Or1ksim.
Of course if you really want to debug the Linux kernel you need to get KDB/KGDB running. You can't use a plain GDB on the kernel, irrespective of the simulator - it gets confused by the memory management. Jeremy -- Tel: +44 (1590) 610184 Cell: +44 (7970) 676050 SkypeID: jeremybennett Email: [email protected] Web: www.embecosm.com _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
