File: debugging.txt

package info (click to toggle)
bart 0.9.00-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 9,040 kB
  • sloc: ansic: 116,116; python: 1,329; sh: 726; makefile: 639; javascript: 589; cpp: 106
file content (44 lines) | stat: -rw-r--r-- 848 bytes parent folder | download | duplicates (6)
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
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44


Running a command in a debugger 
-------------------------------

This involves several (easy) steps:

1. Recompile BART with debugging information. Create
a Makefile.local in the BART directory with the
following line added:

DEBUG=1


Then recompile with:

make allclean
make bart


2. Install the GNU debugger (gdb)


3. Run the failing BART command:

gdb --args bart <command> [<options> ...] <arg1> ...


4. Then type 'run' to start the process.

If it crashes, you are back in the debugger. You can also
type CTRL-C to interrupt it at any time.

In the debugger:

You can type 'bt' to get a backtrace which is helpful to
investigate a segmentation fault or similar.

You can also call functions. For example, this can be used to save
a multi-dimensional array from the debugger like this:

(gdb) call dump_cfl("dbg_img", 16, dims, image)