|
|
24.
|
|
|
reuse a previously created cache dir (CDIR) or, if it does not exist, create it
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:75
|
|
|
25.
|
|
|
report download/install progress when installing packages into sandbox
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:84
|
|
|
26.
|
|
|
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
|
|
|
27.
|
|
|
Install an extra package into the sandbox (can be specified multiple times)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:156 ../bin/apport-valgrind.py:102
|
|
|
28.
|
|
|
Error: %s is not an executable. Stopping.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:133
|
|
|
29.
|
|
|
Do not put the new traces into the report, but write them to stdout.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:48
|
|
|
30.
|
|
|
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
|
|
|
31.
|
|
|
Write modified report to given file instead of changing the original report
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:64
|
|
|
32.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:73
|
|
|
33.
|
|
|
Override report's CoreFile
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:76
|
