- xv6 running remotely on a CS Lab machine
- gdb connected to xv6 with frames and variables showed
- code edited on the local machine and automatically synced
- files on CS Lab machine listed
- documentation (and declared location) shown for the selected function
This tutorial will teach you how to debug xv6 remotely using CLion.
In the screenshot below, I have:
As some of you may already know, we will be allowed to work in pair going forward from P3. I found VSCode Live Share pretty useful for group programming (especially face-to-face paring programming).
Roughly speaking, VSCode Live Share is Google Docs for Coding. It supports
- Live editing
- Focus and Follow
- Audio calls
- Shared terminal
- Shared servers (not covered in this tutorial)
- Group debugging (not covered in this tutorial)
This tutorial teaches you how to set up collaborative debugging for xv6 on Windows using VSCode.
If you haven't installed WSL and/or toolchains for compiling xv6, please refer to my previous tutorial: Compile xv6 Locally on Windows. Also, make sure that you have
gdb
installed on Windows (not just in WSL).
Note: This tutorial is specifically focused on Windows users. Some configuration might not work on other operating systems.
(more…)
I believed that most C programmers have encountered segmentation fault before. In this case, we have to write a lot of print statements or use the command-line tool gdb to find where is wrong. Either way, it's time-consuming to debug your code only using those basic tools.
This tutorial walks you through how to debug on CLion locally while having your code compile and run on remote CS Lab machines.
(more…)
In this tutorial, you will learn how to compile and run xv6 locally on Windows 10 using WSL (Windows Subsystem for Linux)
(more…)