From 52c61961453351733481890fd864ad6add0c30f7 Mon Sep 17 00:00:00 2001 From: Edwin Garcia Date: Mon, 22 Jan 2024 03:54:59 -0600 Subject: [PATCH] docs: improve wording in the "Debug with gdb" section Signed-off-by: Edwin Garcia --- EN/2_mri_structure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EN/2_mri_structure.md b/EN/2_mri_structure.md index 82a6dd1..77df66e 100644 --- a/EN/2_mri_structure.md +++ b/EN/2_mri_structure.md @@ -112,7 +112,7 @@ When modifying the MRI source code, you can easily introduce critical problems t 1. Write in `ruby/test.rb` what you want to check. Note that you can't use gems or extension libraries in `test.rb`. 3. Invoke `$ make gdb` to run miniruby with gdb. If there are no problems, gdb finishes silently. -`make gdb` uses `./miniruby`. If you want to debug with `./ruby`, use `make gdb-ruby` rule. +`make gdb` uses `./miniruby`. If you want to debug with `./ruby`, use `make gdb-ruby` instead. If you want to use break points, modify the `run.gdb` file generated by the `make gdb` command. For example, the `b func_name` gdb command inserts a break point at the beginning of the `func_name` function.