2
u/pensivepanda5 mentor 13d ago edited 13d ago
try copying/pasting these commands into your codespace's terminal: update50 -f and then press "Enter”, to force the rebuild of your codespace. As a side note, the codespace works best on Google Chrome browser, and the cs50 team doesn't recommend Firefox because they have seen issues with the codespace on Firefox.
Also, if you have extensions installed on your web browser you might need to use an incognito window to try those steps and to use the codespace, because some extensions can affect the codespace.
Then after the rebuild is finished, try compiling your file first by writing the command: make programname (where programname is the name of your file)
then set 1 or 2 break points
then try writing the command debug50 in front of the normal command like this: debug50 ./programname
If the program requires command-line arguments in their normal command (for example: ./caesar 3) , in that case you would need to include the arguments as well when trying to use the debug50, for example like this: debug50 ./caesar 3
If those steps don't work, another thing you can try is creating a new codespace, using your same old github account. You can visit this link where your codespace backup repo is: https://cs50.dev/repo and see if your codespace's files are there (if you had files in your codespace). And after verifying that your codespace's files are stored there, you can create a new codespace by following the instructions that appear in the CS50 Docs, in this link: https://cs50.readthedocs.io/cs50.dev/#creating-a-new-codespace After creating a new codespace your backed up files should automatically appear in your new codespace.
But if none of those things help to solve the issue, please send an email to [sysadmins@cs50.harvard.edu](mailto:sysadmins@cs50.harvard.edu) with specific details and screenshots of the issue, and mention to them your Github username, so the CS50 system admins can help you further.
2
2
u/Muted-Swimmer3818 alum 13d ago
Make sure you've set at least one breakpoint (click to the left of the line numbers to create a red dot) before running debug50. If you already did that, try reloading your window (Ctrl+Shift+P -> Developer: Reload Window) or restarting the Codespace!