pylint 3.2.2 fixes: initialize gdb_sandbox and fix UnboundLocalError in add_kernel_crash_info #339
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pylint 3.2.2 complains:
If
options.gdb_sandbox
evaluates to True, the architecture is the system architecture, andsandbox
evaluates to False,gdb_sandbox
will not be set.The case in
apport/report.py
can be hit by analyzing a local kernel crash report with apport-retrace.load_report
inapport-retrace
loads the report withbinary="compressed"
. This leads toVmCore
being an instance ofCompressedValue
which does not have afind
method.Use the high-level interface
tempfile.NamedTemporaryFile
instead oftempfile.mkstemp
and always write theVmCore
content. Add support for writingCompressedValue
. Add unit tests to (hopefully) cover all cases. Note:add_kernel_crash_info
is only called byapport-retrace
.