From c87d05085becdaf6324cdc82355b1a1251d0bffa Mon Sep 17 00:00:00 2001 From: Jidong Xiao Date: Tue, 21 Jan 2025 16:09:51 -0500 Subject: [PATCH] fall 23 to spring 25 --- labs/debugging/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/labs/debugging/README.md b/labs/debugging/README.md index a44a1c6..2aade6d 100644 --- a/labs/debugging/README.md +++ b/labs/debugging/README.md @@ -1,4 +1,4 @@ -# Lab 3 — Memory Diagrams, Testing, and Debugging +# Memory Diagrams, Testing, and Debugging For this lab, you must use a terminal. Do not use IDEs for this lab. @@ -136,7 +136,7 @@ figure out how to do each of the steps below in your debugger of choice. Note that in addition to a standard step-by-step program debugger like gdb/lldb, we also recommend the use of a memory debugger (drmemory or valgrind) for programs with dynamically-allocated memory (we’ll soon talk about this in Lectures), or anytime you have a segmentation fault or other confusing program behavior. We’ll work the memory debugger in lab next week! Information about memory debuggers is available here: -http://www.cs.rpi.edu/academics/courses/fall23/csci1200/memory_debugging.php +http://www.cs.rpi.edu/academics/courses/spring25/csci1200/memory_debugging.php After today’s lab, you should be comfortable with the basics of command line debugging within your preferred development environment. Keep practicing with the debugger on your future homeworks, and be prepared