1282 days, 8 hours, 41 mins ago
For the final project, please note that we cannot look at code for the assignment. When signing up with debugging or code questions, make sure to gather information and explore the issue on your own first using the debugging checklist introduced in class: (1) Observe the issue, (2) Create a reproducible input, (3) Narrow the search space, (4) Analyze, (5) Devise and run experiments, (6) Modify code to resolve the issue. You must fill out the QueueStatus questions with the information you've gathered from this process so far. If you don't provide enough information, we will ask you to go back and gather more information first, and then sign up in the queue again. We can also only answer debugging questions if you have implemented your validate_heap and dump_heap functions to narrow in on the issue you're having - these functions are a huge asset both for you and for us to effectively help you! The spec has details on both of these functions.
1289 days, 8 hours, 22 mins ago
Helper Hours Notes: while we work to help answer your questions, please note that we may have to limit the amount of time we spend with each person as we strive to help as many people as possible. For this reason, we encourage you to prioritize the questions that you need the most help with! When it is your turn to be helped, please join the corresponding Zoom chat as quickly as possible. If you aren't able to join soon after being taken by a TA, we may have to come back to you later and continue helping other students. We appreciate your understanding!
1314 days, 10 hours, 29 mins ago
Beginning with assign3, for debugging questions, you must make sure to gather information and explore the issue on your own first using the debugging checklist discussed in lab and in the assignment spec, and fill out the QueueStatus questions with this information. If you don't provide enough information, we will ask you to please re-sign up in the queue once you can provide more information so that we can better help you. We are looking for information like - what have you observed from running GDB? Have you found a simple, reproducible test case? Etc. If you are eager to sign up for Helper Hours as soon as they open, we recommend preparing responses ahead of time to the questions: "What question do you have? Please provide as much information as possible." and "What steps have you already taken to try and answer your question? (e.g. running gdb/valgrind, reading Resources page, etc.). This information is required for help with debugging questions."
1337 days, 21 hours, 30 mins ago
Welcome to CS107 Helper Hours! Once you've signed up, please wait for a TA to mark you as being helped, and then join that TA's personal office hours Zoom session by logging into Canvas, going to the "Zoom" tab in the sidebar, and joining the session for the current helper hours for that TA. Note that each TA has their own Zoom session for each helper hours, so make sure you join the correct session at the correct time.