Dcc: Difference between revisions

From techdocs
Jump to navigation Jump to search
(Created page with "dcc is used in several CSE courses including COMP1511, COMP1521 & COMP1911. dcc has a https://github.com/COMP1511UNSW/dcc github repo It is manually added to CSE systems as https://gitlab.cse.unsw.edu.au/ccs/extrafiles/-/blob/master/bin/dcc /usr/local/extrafiles/bin/dcc dcc compiles C programs with {{man|clang}} & {{man|gcc}} adding extra explanation to error messages suitable for novice programmers. dcc injects {{man|python3}} into the binary which catches...")
 
No edit summary
 
Line 1: Line 1:
dcc is used in several CSE courses including COMP1511, COMP1521 & COMP1911.
dcc is custom software written by Andrew Taylor used in several CSE courses including COMP1511, COMP1521 & COMP1911.


dcc has a  [[https://github.com/COMP1511UNSW/dcc github repo]]
dcc has a  [[https://github.com/COMP1511UNSW/dcc github repo]]

Latest revision as of 12:14, 23 Haziran 2022

dcc is custom software written by Andrew Taylor used in several CSE courses including COMP1511, COMP1521 & COMP1911.

dcc has a [github repo]

It is manually added to CSE systems as [/usr/local/extrafiles/bin/dcc]

dcc compiles C programs with clang & gcc adding extra explanation to error messages suitable for novice programmers.

dcc injects python3 into the binary which catches run-time errors and invokes gdb to print useful information including a stack backtrace and nearby variable values, all in a form comprehensible to novice programmers.

dcc runs valgrind simultaneously as a separate synchronized process checking for uninitialized variables.

dcc's only dependencies are python3, clang, GCC & valgrind