Gdb: Difference between revisions
From wikinotes
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
|} | |} | ||
</blockquote><!-- Tutorials --> | </blockquote><!-- Tutorials --> | ||
= Related = | |||
<blockquote> | |||
{| class="wikitable" | |||
|- | |||
| [[gdb gui]] || browser-based gui for gdb | |||
|- | |||
|} | |||
</blockquote><!-- Related --> | |||
= In other Languages = | = In other Languages = |
Latest revision as of 03:17, 10 February 2023
Tutorials
gdb in-depth tutorial https://www.sourceware.org/gdb/current/onlinedocs/gdb.html
Related
gdb gui browser-based gui for gdb
In other Languages
python
Usage
gdb python2 run systems/core/myscript.py # when a segfault occurs, you can use the standard # gdb options to display the full backtrace btpython/pyqt gdb extensions
Debian
Debian-based distros have a separate installable package for python/pyqt to be installed with the gdb debugging symbols. I made an entirely separate vagrant build based on ubuntu-server to gain access to this info.sudo apt install python-dbg python-pyqt5-dbg ## pyside-dbg no longer providedArchlinux
NOTE:
The author of qutebrowser manages his own repo with dbg builds of python and pyqt for archlinux. I have not tested them yet, and cannot find the link in my history
Archlinux does not provide a package for this, which means you'll need to compile both python and Qt with appropriate flags. I tried this, but was unsuccessful - (more specifically, I successfully compiled python, but make install replaced my builtin python, and broke my system).