It should be possible to get this development environment running under windows with the help of Cygwin. Install cygwin, and be sure to install the flex and bison packages (they are under the development header). Another alternative is to use virtualization software like VMware and install Linux in a VM.
Most modern Linuxes and BSDs have an ELF toolchain compatible with the labs. That is, the system-standard gcc, as, ld and objdump should just work. The lab makefile should automatically detect this. However, if your machine is in this camp and the makefile fails to detect this, you can override it by adding the following line to conf/env.mk:
If you are using something other than standard x86 Linux or BSD, you will need the GNU C compiler toolchain, configured and built as a cross-compiler for the target 'i386-csl373-elf', as well as the GNU debugger, configured for the i386-csl373-elf toolchain. You can download the specific versions we used via these links, although any recent versions of gcc, binutils, and GDB should work:
Once you've unpacked these archives, run the following commands as root:
# cd binutils-2.20.1 # ./configure --target=i386-csl373-elf --disable-nls # make # make install # cd ../gcc-4.5.1 # ./configure --target=i386-csl373-elf --disable-nls --without-headers \ --with-newlib --disable-threads --disable-shared \ --disable-libmudflap --disable-libssp # make # make install # cd ../gdb-6.8 # ./configure --target=i386-csl373-elf --program-prefix=i386-csl373-elf- \ --disable-werror # make # make install
Then you'll have in /usr/local/bin a bunch of binaries with names like i386-csl373-elf-gcc. The lab makefile should detect this toolchain and use it in preference to your machine's default toolchain. If this doesn't work, there are instructions on how to override the toolchain inside the GNUmakefile in the labs.
qemuon the command line, ensure that the following is added to your
We highly recommend you use a patched version of QEMU instead of the stock version that may come with your distribution. The version installed on the deparment cluster is already patched. To build your own patched version of QEMU:
|debug-seg||Use DS-relative virtual addresses instead of linear addresses in the GDB stub.|
|info-pg||Add "info pg" in the QEMU monitor that prints the page table.|
|triple||On triple fault, dump state and halt for inspection instead of resetting.|
You can access Bochs on the department cluster by ensuring that your
environment variable contains the following path:
We highly recommend you use a patched version of Bochs instead of the stock
version to allow reproducible executions. The version installed on the
department cluster is already patched. There are two executables that
need to be built:
bochs (which is compiled with
an internal debugger) and
bochs-gdb (which is compiled with
gdb-stub for debugging with
these executables have been pre-built on the department cluster.
To build your own patched version
--with-x --with-x11 --with-term --with-noguito
bochsbinary with SMP support that can be used with both
pintos. This bochs binary supports an internal debugger shipped with bochs.
/path/to/bochs-gdb-installfor the install directory to avoid overwriting the previous installation.
/path/to/bochs-gdb-install/bindirectory. Go to this directory and rename the
mv bochs bochs-gdb.
bochsfrom scratch (instead of using our custom tarball), you can download the official 2.4.5 source tarball from the Bochs homepage and apply the following patch series: These patches are designed for use with Bochs 2.4.5:
|jitter||Adds the "jitter" feature, in which timer interrupts are delivered at random (but reproducible) intervals.|
|att||Sets the default disassembly mode to
cdinto the Bochs directory, then type:
--dry-runoption if you want to test whether the patches would apply cleanly before trying to apply them.
cscope/ctagswith vi: Vim/cscope tutorial, Vim/ctags tutorial