15-213 Intro to Computer Systems: Frequently Asked Questions

• Yes.
• Did we say, "Yes"?
• Yes, we did.
• Please read the lab writeups.
• :-)

• Email us at 15-213-staff@cs.cmu.edu.
• Stop by during office hours, Sun-Thu, 5:30-8:30, WeH 5207.
• There is walk-in tutoring for 213 students on Tuesdays, 8:30-11:00pm, Mudge Reading Room.
• Schedule a 1:1 meeting with your instructors or TAs.

• No. Text (copy and paste) is fine.

• After you handin your code, always view it in Autolab to make sure that the indenting is what you expect. If it's not, then there are two possible reasons: (1) Your editor is configured to indent tabs a certain width. (2) You've mixed tabs and spaces in your code.
• In either case, you shoule use spaces instead of tabs. To replace all tabs with spaces, run

  expand -t4 foo.c > bar.c 

• The Linux executable bit is not set. Run "chmod +x <filename>" to set the executable bit.
• This problem may occur if you extract the handout tarball on a Windows machine. Always extract the handout on a Linux machine.

• Run "tar -xvf <filename>" to extract it.

• You don't have an Autolab account for this course yet. Autolab accounts are not tied directly to the Hub like Blackboard accounts.
• Email the staff list 15-213-staff@cs.cmu.edu if you need an account created for you. You must be enrolled in the course in order to get an Autolab account.

• You should be able to access the shark machines with your Andrew credentials. Email the staff list 15-213-staff@cs.cmu.edu if you have trouble.

• Your work will be graded on the shark machines, so it is in your best interest to work there.
• For most labs, you may alternatively work on the Andrew Unix machines, which are nearly identical.
• However, you must complete bomblab and buflab on a shark machine.

• You may attend any recitation you wish as long as the instructor leading the recitation allows it.
• Please make sure the recitation you normally attend is the one specified on your Autolab account; if this is not the case, email the staff list so that we can update your account.

• As we discussed in the writeup, Autolab uses the driver.pl program to grade your submission. The driver.pl program runs dlc to check for operator violations and bddcheck/check.pl to do exhaustive testing. There are three reasons why btest may give different scores than driver.pl:
  • Reason 1: dlc discovered that you used illegal operators or too many operators.
  • Reason 2: btest does not do exhaustive testing. It is mostly useful for testing individual inputs on invidivual puzzles. Use bddcheck/check.pl for final testing.
  • Reason 3: bddcheck/check.pl is finicky about the code formatting, especially the location of the first and last braces in a function. The final right brace must be in the first column.

Bomb Lab

• Please don't submit defusing strings that contain apostrophes. There is a known bug in the backend autograder that causes it to get confused by strings that contain apostrophes. In each of these cases, there is an alternate solution that doesn't contain apostrophes.

• What secret phase?

• On some labs we have set flags (-Wall -Wextra) for the compiler to generate more warnings than usual. We also set a flag (-Werror) to treat warnings as errors.
• Any class of errors that can be detected by the compiler should be addressed sooner rather than later.

• Your main function probably returns something other than 0.
• Our driver checks to make sure your simulator exited successfully, and in C, a main function should return 0 if it exited successfully.

• Reason: you are missing some header files in your include list.
• Fix: Add this to your other includes:

            #include  <getopt.h>
            #include  <stdlib.h>
            #include  <unistd.h>
          

• shark> /usr/bin/telnet

• No, it only needs to support GET requests.

• You're probably reading the data with functions such as getstr or rio_readlineb that are designed for text. Random end-of-line characters in the binary data will cause these functions to terminate prematurely. Use rio_readn and rio_readnb instead.

• You've probably added -std=c99 to your CFLAGS. Leave it out or set it to gnu99 instead.

• Have two terminal windows open, ssh to the same shark, start your proxy in one:

  [myshark]$ ./proxy <portnum>
  

  and do the following in the other:

  [myshark]$ export http_proxy=myshark:<portnum>
  [myshark]$ wget -d www.cnn.com
  

  Note that the "-d" option provides debugging info with exact request/response headers.
• For fine-grain debugging, you can send headers from wget output line by line with nc:

  [myshark]$ nc myshark <portnum>
  GET http://www.cnn.com/ HTTP/1.0
  ...
  

• At the end of the line press Ctrl^V then enter to generate \r. Another enter will generate \n.