I've never used marss with the SDL mode (only -curses). In this mode, you won't have the problem of the cursor getting stuck. One thing I personally do is I have a gdb script that I use especially for marss I call it 'gdbrun'):
handle SIGUSR1 SIGUSR2 nostop noprint b memoryController.cpp:119 info breakpoints run Then you can start up gdb with: gdb -x gdbrun -args -hda xxx -simconfig blah.cfg -curses This will start up a simulation at the terminal without the SDL (visual) mode. I'd throw all your parameters in a simconfig so you don't have to configure them from the monitor console. And you should be good to go. The VM will run as normal and when you start up a sim, the breakpoint will hit as normal and dump you into gdb. Hope that helps, Paul On Thu, Jun 16, 2011 at 12:00 PM, chenlong1014 <[email protected]>wrote: > Hey, > > Has anyone used gdb in Marss before? I got the following questins. > > compile marss with debug: scons -Q debug=1 > then in linux terminal run: > $gdb qemu/qemu-system-x86-64 > to start gdb. > > In gdb, enter > (gdb)b Memory::MemoryController::MemoryController > to set a breakpoint at the constructor of MemoryController > > (gdb)r -hda DiskImageFile > to start the disk image > > (gdb)handle SIGSUR1 SIGSUR2 nostop noprint > to continue boot the disk image. > > Then in the qemu virtual machine, enter > ./start_sim > to run the simulation. > > At this time, the Marss system is stoped and I cannot even quit the > simulation since my mouse is trapped by the qemu. > > Can anyone help me out of this? Thank you very much! > > > Regards, > > Long > 2011-06-16 > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
