|
25.
|
|
|
Destination directory exists and is not empty.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-unpack.py:86
|
|
57.
|
|
|
No pending crash reports. Try --help for more information.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-cli.py:419
|
|
59.
|
|
|
specify the log file name produced by valgrind
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:49
|
|
63.
|
|
|
report download/install progress when installing packages into sandbox
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-valgrind.py:81
|
|
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
|
|
65.
|
|
|
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:99
|
|
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
|
|
69.
|
|
|
Write modified report to given file instead of changing the original report
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:64
|
|
70.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:73
|