|
|
114.
|
|
|
%prog [options] <apport problem report | crash ID>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:37
|
|
|
116.
|
|
|
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
|
|
|
118.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:73
|
|
|
119.
|
|
|
Override report's CoreFile
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:76
|
|
|
120.
|
|
|
Override report's ExecutablePath
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:79
|
|
|
121.
|
|
|
Override report's ProcMaps
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:82
|
|
|
124.
|
|
|
Only unpack the additionally required packages, do not configure them; purge packages again after retracing
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:57
|
|
|
125.
|
|
|
Do not use packaging system when using -u and do not purge packages afterwards. This should only be used for temporarily unpacked chroot tarballs where it would just be a waste of time.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:60
|
|
|
126.
|
|
|
Install an extra package (can be specified multiple times)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:63
|
|
|
127.
|
|
|
Path to a file with the crash database authentication information. This is used when specifying a crash ID to upload the retraced stack traces (only if neither -g, -o, nor -s are specified)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:163
|
