From 6519326e54003663b3b97f0648306834e11c1125 Mon Sep 17 00:00:00 2001 From: Jidong Xiao Date: Sun, 10 Sep 2023 23:56:06 -0400 Subject: [PATCH] emphasize gdb commands --- labs/03_debugging/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/labs/03_debugging/README.md b/labs/03_debugging/README.md index 190f1f3..191e87f 100644 --- a/labs/03_debugging/README.md +++ b/labs/03_debugging/README.md @@ -188,7 +188,7 @@ called the library incorrectly or passed the library bad data. Find the function nearest to the top of the stack that is actually your code. By typing *frame N*, where *N* is the index of the function on the stack, you can examine your code and variables and you can see the line number in your code that caused the crash. Type *info locals* and *info args* to examine the data in the -function. Type list to see the source code. +function. Type *list* to see the source code. 7. Breakpoint on Variable Change: The last powerful debugger feature we will try today is variable monitoring. Add a new modifier member function to the *Point* class named *set_elevation* that changes the *y* coordinate of a *Point* instance. Create an instance of a *Point* object in the *main* function called *pt*.