|
|
2.
|
|
|
specify the log file name produced by valgrind
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:49
|
|
|
3.
|
|
|
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
|
|
|
4.
|
|
|
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
|
|
|
5.
|
|
|
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
|
|
|
6.
|
|
|
report download/install progress when installing packages into sandbox
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:81
|
|
|
7.
|
|
|
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
|
|
|
11.
|
|
|
Report a malfunction to the developers
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.desktop.in.h:2 ../kde/apport-kde-mime.desktop.in.h:2
../kde/apport-kde.desktop.in.h:2
|
|
|
12.
|
|
|
Your system might become unstablenow and might need to be restarted.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../data/kernel_oops.py:29 ../debian/tmp/usr/share/apport/kernel_oops.py:29
|
|
|
13.
|
|
|
Do not put the new traces into the report, but write them to stdout.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:48
|
|
|
14.
|
|
|
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
|
