Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:hig:coredumps [2019/01/26 23:24] – alexxcons | dev:hig:coredumps [2019/03/23 17:08] (current) – grammar blueberrybrownie | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | <note warning> | + | <note warning> |
- | Afaik usually | + | Usually |
- | https:// | + | |
- | Afaik there are (at least) | + | There are (at least) |
1.) Provide a failsafe way to reproduce the crash | 1.) Provide a failsafe way to reproduce the crash | ||
Line 22: | Line 21: | ||
E.g. here some manual for Ubuntu: https:// | E.g. here some manual for Ubuntu: https:// | ||
- | 3.) Enable coredumps, attach the compressed coredump of the crash to the bugtracker, together with the application binary you used. ( debug packages need to be installed, so that the coredump has debug symbols ) | + | 3.) Compile the appliaction with debug symbols, install it and provide a backtrace |
- | + | ||
- | 4.) Compile the appliaction with debug symbols, install it and provide a backtrace | + | |
If all the other options fail, you can still compile stuff from source with debug symbols enabled (e.g. " | If all the other options fail, you can still compile stuff from source with debug symbols enabled (e.g. " | ||
You will need to install the used build environment and all dependencies of the application in dev-version .. the build-tool usually tells what is missing. | You will need to install the used build environment and all dependencies of the application in dev-version .. the build-tool usually tells what is missing. | ||
Reproduce the crash with the self-compiled binary, either via gdb or via coredump, so you get a backtrace which has file-names/ | Reproduce the crash with the self-compiled binary, either via gdb or via coredump, so you get a backtrace which has file-names/ |