Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GDB intro improvements #2200

Merged
merged 1 commit into from
May 23, 2019
Merged

GDB intro improvements #2200

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/code/os-dev.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ To view logs from all your applications you can use `journalctl`. [More info](ht

## Inspecting crashes {#inspecting-crashes}

The [GNU Project Debugger (gdb)](https://www.gnu.org/software/gdb/) can do a lot, but we're mostly going to focus on getting useful information when an application crashes.
The [GNU Project Debugger (gdb)](https://www.gnu.org/software/gdb/) is a general purpose debugger, but we're mostly going to focus on getting useful information when an application crashes.
1. Open an application in gdb, for example AppCenter by running:
```
gdb io.elementary.appcenter
Expand All @@ -143,4 +143,5 @@ The [GNU Project Debugger (gdb)](https://www.gnu.org/software/gdb/) can do a lot
4. Get more information by typing `backtrace` and pressing enter.
5. Please share the lines after `(gdb) backtrace`, those should provide useful information.

For more information see the manpages by running: `man gdb`.
Another tutorial: [Debugging with GDB](https://betterexplained.com/articles/debugging-with-gdb/)