| | 161 | |
| | 162 | === Creating Backtraces === |
| | 163 | |
| | 164 | == General == |
| | 165 | |
| | 166 | Backtraces can be very useful to trouble-shoot issues like segmentation faults. To create a useful backtrace, you need gdb (the GNU Debugger) installed and an application (and possibly libraries) with debugging symbols built in. The following will explain how to do this. |
| | 167 | |
| | 168 | == gdb == |
| | 169 | |
| | 170 | gdb should be part of your distribution just use your favourite way to install the package, e.g. |
| | 171 | |
| | 172 | {{{ |
| | 173 | apt-get gdb |
| | 174 | }}} |
| | 175 | |
| | 176 | for Debian and friends (such as Ubuntu) or |
| | 177 | |
| | 178 | {{{ |
| | 179 | yum gdb |
| | 180 | }}} |
| | 181 | |
| | 182 | for Fedora/RedHat/Mandriva |
| | 183 | |
| | 184 | |
| | 185 | == mondoarchive/mondorescue with debugging symbols == |
| | 186 | |
| | 187 | To get mondoarchive and mondorescue with debugging symbols built in, you need to build from the source. |
| | 188 | |
| | 189 | Get the latest stable mondo source package from ftp://ftp.mondorescue.org/src/, e.g. mondo-2.0.9.tar.gz, unpack: |
| | 190 | |
| | 191 | {{{ |
| | 192 | tar xvzf mondo-2.0.9.tar.gz |
| | 193 | }}} |
| | 194 | |
| | 195 | enter into the new directory and build using make: |
| | 196 | |
| | 197 | {{{ |
| | 198 | cd mondo-2.0.9 |
| | 199 | make |
| | 200 | }}} |
| | 201 | |
| | 202 | You will end up with binary in the following locations which are non-stripped, i.e. they contain debugging symbols: |
| | 203 | {{{ |
| | 204 | file |
| | 205 | }}} |
| | 206 | |
| | 207 | and |
| | 208 | |
| | 209 | {{{ |
| | 210 | file |
| | 211 | }}} |
| | 212 | |
| | 213 | Make backups of the original mondoarchive and mondorestore binaries and copy they newly created over the original ones. |
| | 214 | |
| | 215 | == mondoarchive == |
| | 216 | |
| | 217 | == mondorestore == |
| | 218 | |