aaron/c0db
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

changes for consistency

Browse Source
This commit is contained in:
Aaron Gutierrez
2015-05-06 15:52:58 -04:00
parent 9f4ae3633d
commit 0e1775fcf3
4 changed files with 20 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
final/final.pdf Normal file
View File

Binary file not shown.

29
final/final.tex
View File

@@ -33,7 +33,8 @@
\begin{center} \begin{center}
{\Huge Final Report}\\ {\Huge Final Report}\\
\vspace{10 mm} \vspace{10 mm}
{\Huge The {\tt C0} Debugger}\\ {\Huge {\tt c0db}\\[.4em]
The {\tt C0} Debugger}\\
\vspace{10 mm} \vspace{10 mm}
Submitted to\\ Submitted to\\
@@ -65,9 +66,9 @@ Carnegie Mellon University\\
Finding problems in code is a difficult and time consuming task, one especially Finding problems in code is a difficult and time consuming task, one especially
difficult for programmers learning a new language. To help students more quickly difficult for programmers learning a new language. To help students more quickly
find bugs and understand how their programs run, we created an online debugger find bugs and understand how their programs run, we created an online debugger
for the {\tt C0} programming language. The {\tt C0} debugger enables users to for the {\tt C0} programming language. The {\tt C0} debugger, {\tt c0db},
run programs in their browser and break apart the execution when they don't run enables users to run programs in their browser and break apart the execution
correctly. when they don't run correctly.
\end{titlepage} \end{titlepage}
\pagenumbering{roman} \pagenumbering{roman}
@@ -88,15 +89,15 @@ development we were unable to receive significant use feedback from students.
That said, we were able to gather feedback and support from current 15-122 That said, we were able to gather feedback and support from current 15-122
course staff. course staff.
In terms of our original vision, the {\tt C0} debugger includes almost every In terms of our original vision, {\tt c0db} includes almost every feature we
feature we planned to implement. Users can input code and either run the program planned to implement. Users can input code and either run the program straight
straight through or step through execution instruction by instruction. The only through or step through execution instruction by instruction. The only
significant feature that is not currently implemented completely is breakpoints. significant feature that is not currently implemented completely is
Implementing breakpoints turned out to be significantly more difficult than we breakpoints. Implementing breakpoints turned out to be significantly more
anticipated, and given our limited time frame, we were unable to come up with an difficult than we anticipated, and given our limited time frame, we were unable
adequate solution. We are currently working with Rob Simmons, 15-122 instructor to come up with an adequate solution. We are currently working with Rob
and maintainer for the {\tt C0} language standard, to extend the language to Simmons, 15-122 instructor and maintainer for the {\tt C0} language standard,
support breakpoints more easily going forward. to extend the language to support breakpoints more easily going forward.
\begin{figure}[h] \begin{figure}[h]
\includegraphics[width=\linewidth]{new-gantt} \includegraphics[width=\linewidth]{new-gantt}
@@ -107,7 +108,7 @@ Relative to our revised Gantt Chart (Figure \ref{gantt}) we hit every milestone
on time. Both the front-end and back-end teams completed their tasks by the end on time. Both the front-end and back-end teams completed their tasks by the end
of April, at which point we transitioned everyone to user testing, revisions, of April, at which point we transitioned everyone to user testing, revisions,
and polishing. Both teams were able to recover from the lag reported in our and polishing. Both teams were able to recover from the lag reported in our
progress report to complete the {\tt C0} debugger. progress report to complete {\tt c0db}.
\section{Discussion} \section{Discussion}

BIN
final/letter.pdf
View File

Binary file not shown.

9
final/letter.tex
View File

@@ -19,8 +19,9 @@
\vspace{5mm} \vspace{5mm}
Included with this letter is our team's final report for the browser-based Included with this letter is our team's final report for the browser-based
debugger for the c0 language called c0db. The purpose of the report is to debugger for the {\tt C0} language called {\tt c0db}, the {\tt C0} Debugger.
update you on our progress and to explain and discuss our results. The purpose of the report is to update you on our progress and to explain and
discuss our results.
The report describes the problem addressed by our project, our approach to The report describes the problem addressed by our project, our approach to
solve it, the results we were able to achieve, our challenges and struggles, solve it, the results we were able to achieve, our challenges and struggles,
@@ -31,10 +32,10 @@ existing platform.
If you have any further questions or comments, please contact us at If you have any further questions or comments, please contact us at
shyamsur@andrew.cmu.edu.\\ shyamsur@andrew.cmu.edu.\\
Sincerely,\\\\\\\\ Sincerely,\\[4em]
Shyam Raghavan Shyam Raghavan
\encl{project final paper for c0db} \encl{project final paper for {\tt c0db}}
\end{letter} \end{letter}
\end{document} \end{document}