summaryrefslogtreecommitdiff
path: root/gdb/backtrace.mdwn
blob: a8825d3b58bdf1d0962b35d3e3e6a2c37a94f0c2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
[[meta copyright="Copyright © 2007 Free Software Foundation, Inc."]]
[[meta license="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled
[[GNU_Free_Documentation_License|/fdl]]."]]

When someone asks you to supply a backtrace (from a [[segmentation_fault]], for
example), here is roughly what you have to do.

Run the faulting program like this:

    $ gdb --args PROGRAM [ARGUMENTS]
    [...]
    (gdb) run
    [...]
    [Segmentation fault.]
    (gdb) bt
    [...]

(!) This will only provide useful information if the executable (and additional
libraries) contain debugging symbols, or those are available separartely.

If you're one a [[Debian_GNU/Hurd_system|hurd/running/debian]], you'll have
to have the *hurd-dbg* package installed for debugging Hurd stuff, and perhaps
*libc0.3-dbg* as well if it's inside the glibc.