![how to install gdb in arch linux how to install gdb in arch linux](https://www.ordinatechnic.com/static/distribution-specific-guides/arch/an-arch-linux-installation-on-a-btrfs-filesystem-with-snapper-for-system-snapshots-and-rollbacks/images/optimized/download-1-optimized.jpg)
![how to install gdb in arch linux how to install gdb in arch linux](https://miloserdov.org/wp-content/uploads/2018/08/53.jpg)
The backtrace line from above now has more info: #2 0x00007fbcffc1c091 in g_async_queue_pop_intern_unlocked ( Now start gdb again and look for other missing debug symbols. Install that package sudo apt-get install libglib2.0-0-dbgsym It'll print a few lines, and if you successfully added debian-debug you'll see the package libglib2.0-0-dbgsym - debug symbols for libglib2.0-0 Now search for that package using apt-cache: apt-cache search libglib2.0-0 You'll get a line which starts like libglib2.0-0:amd64 Quit gdb using q and find out which package the shared object belongs to by typing dpkg -S /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 The two question marks ? mean that you don't have the debug symbols for libglib-2.0.so.0 installed. In the shell so gdb prints the backtrace which has many lines that look like #2 0x00007f688c21b091 in ? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 To create a backtrace type thread apply all bt It now (in our case) hopefully crashes and you get back to the gdb shell. In this example we run evince with a file path as argument: gdb -args /usr/bin/evince /home/user/Documents/report.pdf Now install the debugger (gdb): sudo apt-get install gdb
HOW TO INSTALL GDB IN ARCH LINUX UPDATE
Update apt so it will find the packages: sudo apt-get update If needed, replace testing-debug with your release, i.e. To get them, first add the debug package of your release to /etc/apt/sources.list: Most packages have a -dbgsym or -dbg variant which are in the debian-debug packages.