-
Notifications
You must be signed in to change notification settings - Fork 709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault
with the version 0.1.58
on Debian 10 and Ubuntu 20.04 machines
#7718
Comments
Procedure applied:
The compilation of all the profiles has been done with this env:
and the command Result:The first bad commit is c233c92 More tests
and building with the same env and same machine, the Same result if the commit is reverted on |
With this patch-file, the
|
Can you run the |
The full |
Let's try running it as |
Same segfault
Please take note that the report is written on disk and usage without any problems. |
Unfortunately I don't see anything obvious. Maybe @jan-cerny or @evgenyz can think of something here. Note that the report is written on disk so it somehow finishes the scan. |
I'm trying to run the scanner in
A problem with the scanner in the
|
With this patch in the scanner, the segfault disapears:
I know that this shall not be done, but at least we can narrow down the problem... Maybe |
Is this OK that the |
With this, the scanner is OK and the
I will make the PR on the scanner repo and link here. |
Thank you for all the effort you put narrowing down the issue. |
Description of problem:
When doing a
xccdf eval
on a Debian 10 and Ubuntu 20.04 machines, the scanner willsegfault
if using the version0.1.58
, but will run normally when using the version0.1.57
.Note that the
report.html
file is written OK on disk, and usable without any problems.The scanner is the same between runs, build from source, version 1.3.5.
The scanner has been also compiled on CentOS 8, and is working with versions
0.1.57
and0.1.58
.Given that:
0.1.57
is working on Debian and Ubuntu0.1.58
is not working on Debian and Ubuntu0.1.57
and0.1.58
are working on CentOSmaster
(57fc344) is not working, I suspect that some changes in the
ComplianceAsCode/content
between0.1.57
and0.1.58
has been done affecting only the Debian familly, and is not patched in the current master branch.I would like to have some guidance regarding on how to proceed and help finding the source of the issue.
I plan to investigate the issue by compiling myself the version
0.1.57
and0.1.58
, re-test them, andgit bisect
/recompile until one commit is identified.PS: exactly the same behaviour is seen with the
Debian 11
file in the PR #7715. I thought that it could be an issue with my PR, but not sure anymore.SCAP Security Guide Version:
Working one:
Not working one:
Operating System Version:
Steps to Reproduce:
Actual Results:
The not working scan:
The working scan:
Expected Results:
Not
segfault
The text was updated successfully, but these errors were encountered: