From 5b4be018bbbe539f180d8c596e9e94f99f4a844a Mon Sep 17 00:00:00 2001 From: Delyan Angelov Date: Tue, 19 Jul 2022 15:46:53 +0300 Subject: [PATCH] Add a https://github.com/lazalong/V-Hello link. --- ...bleshooting-(debugging)-executables-created-with-V-in-GDB.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Troubleshooting-(debugging)-executables-created-with-V-in-GDB.md b/Troubleshooting-(debugging)-executables-created-with-V-in-GDB.md index 1bedebe..54afe03 100644 --- a/Troubleshooting-(debugging)-executables-created-with-V-in-GDB.md +++ b/Troubleshooting-(debugging)-executables-created-with-V-in-GDB.md @@ -1,3 +1,5 @@ +[A minimal V project using VS Code, mingw gcc and gdb, containing .vscode/ with settings](https://github.com/lazalong/V-Hello) - https://github.com/lazalong/V-Hello + First, it is best to compile your V programs with `-keepc`, and use either `-cg` or `-g` so that the executables will have more debugging information/symbols in them. `-cg` is better, if you are trying to debug C interoperation, because you will avoid the mental context switches while debugging, seeing everything in one large generated C file.