You should add the path "c:\mingw\bin" in your environment variable. This way whenever you type gdb on command prompt, it would search from the above path.
And the same for valgrind?
Till date Valgrind does not run on Windows platform.
Answer from Mantosh Kumar on Stack OverflowGNU Project
sourceware.org › gdb › current › onlinedocs › gdb.html › Source-Path.html
Source Path (Debugging with GDB)
When searching for source files on MS-DOS and MS-Windows, where absolute paths start with a drive letter (e.g. C:/project/foo.c), GDB will remove the drive letter from the file name before appending it to a search directory from source path; for instance if the executable references the source file C:/project/foo.c and source path is set to D:/mnt/cross, then GDB will search in the following locations for the source file:
Videos
Install GCC Compiler & GDB Debugger for C/C++ on Windows ...
11:22
How to Install C/C++ Toolset (GCC G++ GDB) on Windows 11 | Complete ...
03:52
Easy C Debugging with VSCode & GDB - YouTube
03:13
How to install gdb in windows 10 - YouTube
01:42
Path configuration in windows for MingW and GDB. - YouTube
Medium
medium.com › @pamirghimire › debugging-with-gdb-on-windows-using-visual-studio-code-81ba70b562f3
Debugging with GDB on Windows using Visual Studio Code | by Pamir Ghimire | Medium
June 6, 2020 - So MinGW is the GCC port for Windows ... installation comes GDB, a classic debugger for C/C++ [2]. You can find it at path\\to\\MinGW\\bin\\gdb.exe`. So now you have a C/C++ compiler and a debugger....
GNU Project
sourceware.org › gdb › current › onlinedocs › gdb.html › Working-Directory.html
Working Directory (Debugging with GDB)
If you work on a system where GDB supports the info proc command (see Process Information), you can use the info proc command to find out the current working directory of the debuggee.
Top answer 1 of 4
4
There are multiple ways of doing this. The easiest is to check whether gdb is in your $PATH:
which -a gdb
However, the program could be installed and not in your user's $PATH. To quickly search for an executable called gdb do this:
locate -eb '\gdb'
From man locate:
NAME
locate - find files by name
-b, --basename
Match only the base name against the specified
patterns. This is the opposite of --whole‐
name.
-e, --existing
Print only entries that refer to files exist‐
ing at the time locate is run.
EXAMPLES
To search for a file named exactly NAME (not *NAME*),
use
locate -b '\NAME'
Because \ is a globbing character, this disables the
implicit replacement of NAME by *NAME*.
2 of 4
1
That literally means gdb isn't in $PATH or is not executable.
But yeah it should be installed to /usr/bin/gdb which would be in the PATH and the directory /etc/gdb should exist.
Moreover, the usual, which distro are you using?
Kansas State University
textbooks.cs.ksu.edu › cis308 › 0-chapter › 0_5-debugging › tele.html
Debugging C programs :: CIS 308 Textbook
February 16, 2023 - Click Start, type Environment variables, and select “Edit the system environment variables”). Click “Environment Variables..”, then find Path under System variables and click “Edit…”. Look to see if the location of your gdb.exe ...
GitHub
github.com › microsoft › vscode-cpptools › issues › 3076
miDebuggerPath value when gdb is in Windows PATH · Issue #3076 · microsoft/vscode-cpptools
January 23, 2019 - You switched accounts on another tab or window. Reload to refresh your session. ... debuggerfixedCheck the Milestone for the release in which the fix is or will be available.Check the Milestone for the release in which the fix is or will be available. ... Building and debugging any C program using MINGW64, when miDebuggerPath in launch.json is unspecified or set to "gdb", results in the error below. System PATH variable has gdb.exe.
Published Jan 23, 2019
OGG
rpg.hamsterrepublic.com › ohrrpgce › GDB_on_Windows
GDB on Windows
MinGW distributes a Windows version of gdb. You can get the latest mingw installer here which can in turn install gdb. After installing MinGW, run the "MinGW Installation Manager" (which for me was located in C:\MinGW\libexec\mingw-get\guimain.exe ) and then make sure that the mingw32-gdb bin package is installed. (These instructions are for mingw32, not the mingw-w64 fork. But gdb from mingw-w64 should work too.)
GNU
ftp.gnu.org › old-gnu › Manuals › gdb › html_node › gdb_48.html
Debugging with GDB - Source Path
When you start GDB, its source path includes only `cdir' and `cwd', in that order. To add other directories, use the directory command. ... Add directory dirname to the front of the source path. Several directory names may be given to this command, separated by `:' (`;' on MS-DOS and MS-Windows, where `:' usually appears as part of absolute file names) or whitespace.
Dzyoba
alex.dzyoba.com › blog › gdb-source-path
How to point GDB to your sources | There is no magic here
You can direct GDB to the new source path right in the debug session with directory <dir> command: (gdb) list 6 ./Programs/python.c: No such file or directory. (gdb) directory /usr/src/python Source directories searched: /usr/src/python:$cdir:$cwd (gdb) list 6 #ifdef __FreeBSD__ 7 #include <fenv.h> 8 #endif 9 10 #ifdef MS_WINDOWS 11 int 12 wmain(int argc, wchar_t **argv) 13 { 14 return Py_Main(argc, argv); 15 }
Super User
superuser.com › questions › 1396155 › where-does-gdb-get-installed-to-when-using-wsl-in-vs-code
windows subsystem for linux - Where does gdb get installed to when using WSL in VS Code? - Super User
What would my path be? ... This bug report might be relevant for your question. ... Try C:/dev/GDB/gdb.exe. ... He’s referring to gdb, the GNU Debugger. He only misspelled it every time except once. // It most certainly won’t be at C:\dev when he used WSL to install it. ... "C:\Users\jamie\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\usr\bin\gdb" ... Find the answer to your question by asking.
VisualGDB
visualgdb.com › gdbreference › commands › set_solib-search-path
GDB Command Reference - set solib-search-path command
The default value for the solib-search-path variable is "." that corresponds to the working directory of GDB (directory where GDB was launched unless changed using the cd command).
Top answer 1 of 4
33
Use the info source command to get info for the current stack frame.
Here is an example of its output:
(gdb) info source Current source file is /build/gtk+2.0-LJ3oCC/gtk+2.0-2.24.30/modules/input/gtkimcontextxim.c Located in /home/sashoalm/Desktop/compile/gtk+2.0-2.24.30/modules/input/gtkimcontextxim.c Contains 1870 lines. Source language is c. Producer is GNU C11 5.3.1 20160225 -mtune=generic -march=i686 -g -g -O2 -O2 -fstack-protector-strong -fPIC -fstack-protector-strong. Compiled with DWARF 2 debugging format. Does not include preprocessor macro info.
2 of 4
3
Excellent answer from Ciro Santill. However, the script needed a small correction to work with my gdb 8.0.1.
I also changed it to copy the text to the clipboard so I can use it in vim straight away. It works nicely with file_line.vim plugin. This is an example of the clipboard content produced by the script:
/home/ops1/projects/test01/main.cpp:5
The script is below:
import pyperclip
class Clippath (gdb.Command):
"""print absolute path"""
def __init__(self):
super(Clippath, self).__init__("clippath", gdb.COMMAND_USER)
def invoke(self, arg, from_tty):
symtabline = gdb.selected_frame().find_sal()
pyperclip.copy(symtabline.symtab.fullname() + ":" + str(symtabline.line))
Clippath()
Here are the steps to make it all work:
- Install pyperclip python library sudo zypper in python3-pyperclip
- Save the script above to a file, say file-path.py and copy it to ~/.gdb
- Update ~/.gdbinit with adding the following lines: source ~/.gdb/file-path.py
- Now you can copy the path and line to the clipboard with
clippathin gdb
And read more about GDB Python API - link
GNU Project
sourceware.org › gdb › current › onlinedocs › gdb.html › Environment.html
Environment (Debugging with GDB)
Add directory to the front of the PATH environment variable (the search path for executables) that will be passed to your program. The value of PATH used by GDB does not change. You may specify several directory names, separated by whitespace or by a system-dependent separator character (‘:’ on Unix, ‘;’ on MS-DOS and MS-Windows).
Desy
zeuthen.desy.de › unix › unixguide › infohtml › gdb › Source-Path.html
Source Path - Debugging with GDB
When you start gdb, its source path includes only `cdir' and `cwd', in that order. To add other directories, use the directory command. The search path is used to find both program source files and gdb script files (read using the `-command' option and `source' command).
Visual Studio Code
code.visualstudio.com › docs › cpp › cpp-debug
Debug C++ in Visual Studio Code
November 3, 2021 - To debug a memory dump, open your launch.json file and add the coreDumpPath (for GDB or LLDB) or dumpPath (for the Visual Studio Windows Debugger) property to the C++ Launch configuration, set its value to be a string containing the path to the memory dump. This will even work for x86 programs being debugged on an x64 machine. If there are additional directories where the debugger can find symbol files (for example, .pdb files for the Visual Studio Windows Debugger), they can be specified by adding the additionalSOLibSearchPath (for GDB or LLDB) or symbolSearchPath (for the Visual Studio Windows Debugger).
Ubc
clouds.eos.ubc.ca › ~phil › docs › gdb › onlinedocs › gdb_9.html
Debugging with GDB: Source
When you start GDB, its source path includes only `cdir' and `cwd', in that order. To add other directories, use the directory command. The search path is used to find both program source files and GDB script files (read using the `-command' option and `source' command).
Code::Blocks
forums.codeblocks.org › index.php
Where to find "gdb.exe" ?
Where to find "gdb.exe" ? « previous next » · Send this topic · Print · Pages: [1] Go Down · Send this topic · Print · Pages: [1] Go Up · « previous next » · Code::Blocks Forums » · User forums » · Help » · Where to find "gdb.exe" ? XHTML · RSS ·
Top answer 1 of 2
1
No idea what MinGW Installation Manager is or why you were trying to use it when you are using msys2.
To install mingw64 gdb in msys2, you really just need to:
pacman -S mingw-w64-x86_64-gdb
You should probably run pacman -Syu twice before you run the above though.
As you can see, if you need other mingw64 builds of programs (toolchain programs or not), their package names would be prefixed with mingw-w64-x86_64-. There's also the package group mingw-w64-x86_64-toolchain which you can pacman -S --needed instead to get a somewhat full toolchain.
You may also want to use the urt64 toolchain instead. See this page for more details. (You can e.g. pacman -Ss gdb to find out what's the package name prefix for each of the variants.)
Note that to use any of the toolchain (or any non-msys2 builds of programs), you should use the corresponding "launcher" of shell/terminal instead of msys2.exe.
2 of 2
0
Check by restarting your PC, if it didn't work download the *.gdb file from its website (I guess it's a *.rar or some file), now update with MSYS and restart. It have solved for me, I guess it helps....