CT 301 Lab Machines with Debugging

CT 301: C++ Fundamentals · Summer 2026

Lab Machines with Debugging

Use one of the machines below to run gdb (directly or through the VS Code debugger). On other CS lab machines, debugging may still be blocked by a system setting. Avoid denver (CS IT asked us not to use it).

Before you connect:

Connect to the CSU VPN first.
Use the fully qualified name when connecting (for example, lima.cs.colostate.edu, not just lima).
Check current load on the machine stats page. The list there changes; always pick a low-load machine.

Lab 120

(denver is in this lab but should not be used.)

albany

      annapolis

      atlanta

      augusta

      austin

      baton-rouge

      bismarck

      boise

      boston

      carson-city

      charleston

      cheyenne

      columbia

      columbus-oh

      concord

      des-moines

      dover

      frankfort

      harrisburg

      hartford

      helena

      honolulu

      indianapolis

      jackson

      jefferson-city

      juneau

      lansing

      lincoln

      little-rock

      madison

      montgomery

      montpelier

      nashville

      oklahoma-city

      olympia

      phoenix

      pierre

      providence

      raleigh

      richmond

      sacramento

      saint-paul

      salem

      salt-lake-city

      santa-fe

      springfield

      tallahassee

      topeka

      trenton

Lab 215

      ankara
baghdad
bangkok
beijing
berlin
bogota
cairo
damascus
dhaka
hanoi
hong-kong
jakarta
kabul
kinshasa
lima
london
madrid
mexico-city
moscow
pyongyang
riyadh
santiago
seoul
singapore
tehran
tokyo
    

Lab 315

      ant
antlion
aphid
assassin-bug
bee
centipede
cockroach
cricket
damselfly
deer-fly
dragonfly
dung-beetle
flea
hornet
katydid
ladybug
lice
maggot
mosquito
moth
preying-mantis
scorpion
termite
tick
wasp
weevil
    

Always check the machine stats page for the up-to-date list and current load. This handout reflects the lab membership at the time it was written and may change.