lab0-c

Assessing Your C Programming Skills

This lab will give you practice in the style of programming you will need to be able to do proficiently, especially for the later assignments in the class. The material covered should all be review for you. Some of the skills tested are:

• Explicit memory management, as required in C.
• Creating and manipulating pointer-based data structures.
• Working with strings.
• Enhancing the performance of key operations by storing redundant information in data structures.
• Implementing robust code that operates correctly with invalid arguments, including NULL pointers.

The lab involves implementing a queue, supporting both last-in, first-out (LIFO) and first-in-first-out (FIFO) queueing disciplines. The underlying data structure is a circular doubly-linked list, enhanced to make some of the operations more efficient.

Prerequisites

There are a few prerequisites which must be installed on your machine before you will be able to build and run the autograders.

The following command will install all required and optional dependencies on Ubuntu Linux 20.04 or later:

$ sudo apt install build-essential git clang-format cppcheck aspell colordiff valgrind

Note: Cppcheck version must be at least 1.90, otherwise it might report errors with false positives. You can get its version by executing $ cppcheck --version. Check Developer Info for building Cppcheck from source. Alternatively, you can make use of snap for latest Cppcheck:

$ sudo snap install cppcheck
$ export PATH=/snap/bin:$PATH

Integrate clang-format to vim

If you want to run clang-format automatically after saving with vim, clang-format supports integration for vim according to Clang 11 documentation.

By adding the following into $HOME/.vimrc

function! Formatonsave()
  let l:formatdiff = 1
  py3f <path to your clang-format.py>/clang-format.py
endfunction
autocmd BufWritePre *.h,*.hpp,*.c,*.cc,*.cpp call Formatonsave()

Note: on Ubuntu Linux 18.04, the path to clang-format.py is /usr/share/vim/addons/syntax/.

Running the autograders

Before running the autograders, compile your code to create the testing program qtest

$ make

Check the correctness of your code, i.e. autograders:

$ make test

Check the example usage of qtest:

$ make check

Each step about command invocation will be shown accordingly.

Check the memory issue of your code:

$ make valgrind

• Modify ./.valgrindrc to customize arguments of Valgrind
• Use $ make clean or $ rm /tmp/qtest.* to clean the temporary files created by target valgrind

Extra options can be recognized by make:

• VERBOSE: control the build verbosity. If VERBOSE=1, echo eacho command in build process.
• SANITIZER: enable sanitizer(s) directed build. At the moment, AddressSanitizer is supported.

Using qtest

qtest provides a command interpreter that can create and manipulate queues.

Run $ ./qtest -h to see the list of command-line options

When you execute $ ./qtest, it will give a command prompt cmd> . Type "help" to see a list of available commands.

Files

You will handing in these two files

• queue.h : Modified version of declarations including new fields you want to introduce
• queue.c : Modified version of queue code to fix deficiencies of original code

Tools for evaluating your queue code

• Makefile : Builds the evaluation program qtest
• README.md : This file
• scripts/driver.py : The driver program, runs qtest on a standard set of traces
• scripts/debug.py : The helper program for GDB, executes qtest without SIGALRM and/or analyzes generated core dump file.

Helper files

• console.{c,h} : Implements command-line interpreter for qtest
• report.{c,h} : Implements printing of information at different levels of verbosity
• harness.{c,h} : Customized version of malloc/free/strdup to provide rigorous testing framework
• qtest.c : Code for qtest

Trace files

• traces/trace-XX-CAT.cmd : Trace files used by the driver. These are input files for qtest.
  • They are short and simple.
  • We encourage to study them to see what tests are being performed.
  • XX is the trace number (1-17). CAT describes the general nature of the test.
• traces/trace-eg.cmd : A simple, documented trace file to demonstrate the operation of qtest

Debugging Facilities

Before using GDB debug qtest, there are some routine instructions need to do. The script scripts/debug.py covers these instructions and provides basic debug function.

$ scripts/debug.py -h
usage: debug.py [-h] [-d | -a]

optional arguments:
  -h, --help     show this help message and exit
  -d, --debug    Enter gdb shell
  -a, --analyze  Analyze the core dump file

• Enter GDB without interruption by SIGALRM.

$ scripts/debug.py -d
Reading symbols from lab0-c/qtest...done.
Signal        Stop	Print	Pass to program	Description
SIGALRM       No	No	No		Alarm clock
Starting program: lab0-c/qtest 
cmd> 

• When qtest encountered Segmentation fault while it ran outside GDB, we could invoke GDB in the post-mortem debugging mode to figure out the bug.

  The core dump file was created in the working directory of the qtest.

  • Allow the core dumps by using shell built-in command ulimit to set core file size.

  $ ulimit -c unlimited
  $ ulimit -c
  unlimited
  

  • Enter GDB and analyze

  $ scripts/debug.py -a
  Reading symbols from lab0-c/qtest...done.
  [New LWP 9424]
  Core was generated by `lab0-c/qtest'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 ...
  #1 ... (backtrace information)
  #2 ...
  (gdb) 
  

User-friendly command line

linenoise was integrated into qtest, providing the following user-friendly features:

• Move cursor by right and left key
• Get previous or next command typed before by up and down key
• Auto completion by TAB

License

lab0-c is released under the BSD 2 clause license. Use of this source code is governed by a BSD-style license that can be found in the LICENSE file.

External source code:

• dudect: public domain
• git-good-commit: MIT License
• linenoise: BSD 2-Clause "Simplified" License