|
|
3.
|
|
|
Start an interactive gdb session with the report's core dump (-o ignored; does not rewrite report)
|
|
|
|
|
Start an interactive gdb session with the report's core dump (-o ignored; does not rewrite report)
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
../bin/apport-retrace.py:55
|
|
|
4.
|
|
|
Write modified report to given file instead of changing the original report
|
|
|
|
|
Write modified report to given file instead of changing the original report
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
../bin/apport-retrace.py:64
|
|
|
5.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
../bin/apport-retrace.py:73
|
|
|
6.
|
|
|
Override report's CoreFile
|
|
|
|
|
Override report's CoreFile
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
../bin/apport-retrace.py:76
|
|
|
7.
|
|
|
Override report's ExecutablePath
|
|
|
|
|
Override report's ExecutablePath
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
../bin/apport-retrace.py:79
|
|
|
8.
|
|
|
Override report's ProcMaps
|
|
|
|
|
Override report's ProcMaps
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
../bin/apport-retrace.py:82
|
|
|
9.
|
|
|
Rebuild report's Package information
|
|
|
|
|
Rebuild report's Package information
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
../bin/apport-retrace.py:88
|
|
|
10.
|
|
|
Build a temporary sandbox and download/install the necessary packages and debug symbols in there; without this option it assumes that the necessary packages and debug symbols are already installed in the system. The argument points to the packaging system configuration base directory; if you specify "system", it will use the system configuration files, but will then only be able to retrace crashes that happened on the currently running release.
|
|
|
|
|
Build a temporary sandbox and download/install the necessary packages and debug symbols in there; without this option it assumes that the necessary packages and debug symbols are already installed in the system. The argument points to the packaging system configuration base directory; if you specify "system", it will use the system configuration files, but will then only be able to retrace crashes that happened on the currently running release.
|
|
Translated and reviewed by
Rafael Neri
|
|
|
|
Located in
../bin/apport-retrace.py:95
|
|
|
11.
|
|
|
Build another temporary sandbox for installing gdb and its dependencies using the same release as the report rather than whatever version of gdb you have installed.
|
|
|
|
|
Build another temporary sandbox for installing gdb and its dependencies using the same release as the report rather than whatever version of gdb you have installed.
|
|
Translated and reviewed by
Dawid Wiktor
|
|
|
|
Located in
../bin/apport-retrace.py:109
|
|
|
12.
|
|
|
Report download/install progress when installing packages into sandbox
|
|
|
|
|
Report download/install progress when installing packages into sandbox
|
|
Translated and reviewed by
Rafael Neri
|
|
|
|
Located in
../bin/apport-retrace.py:119
|
