|
|
12.
|
|
|
Send an error report to help fix this problem
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.ui.h:5
|
|
|
59.
|
|
|
specify the log file name produced by valgrind
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:49
|
|
|
60.
|
|
|
reuse a previously created sandbox dir (SDIR) or, if it does not exist, create it
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:55
|
|
|
61.
|
|
|
do not create or reuse a sandbox directory for additional debug symbols but rely only on installed debug symbols.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:63
|
|
|
62.
|
|
|
reuse a previously created cache dir (CDIR) or, if it does not exist, create it
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:72
|
|
|
64.
|
|
|
the executable that is run under valgrind's memcheck tool for memory leak detection
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../debian/tmp/usr/bin/apport-valgrind.py:62 ../bin/apport-valgrind.py:62
|
|
|
67.
|
|
|
Do not put the new traces into the report, but write them to stdout.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:48
|
|
|
68.
|
|
|
Start an interactive gdb session with the report's core dump (-o ignored; does not rewrite report)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:55
|
|
|
70.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:73
|
|
|
74.
|
|
|
Rebuild report's Package information
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:88
|
