Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[22.4.1] gsad crash on start when using gvm-lib 22.4.3 #115

Closed
tuxmaster5000 opened this issue Feb 9, 2023 · 3 comments · Fixed by greenbone/gvm-libs#737
Closed

[22.4.1] gsad crash on start when using gvm-lib 22.4.3 #115

tuxmaster5000 opened this issue Feb 9, 2023 · 3 comments · Fixed by greenbone/gvm-libs#737
Labels
bug Something isn't working

Comments

@tuxmaster5000
Copy link

Expected behavior

That the daemon starts

Actual behavior

It will crash with Segmentation fault (core dumped)

Steps to reproduce

  1. gsad -f

GVM versions

gvm-libs: 22.4.3

Environment

Operating system: CentOS 8 Stream

Hint:
Build with gvm-libs 22.4.2 will work.
@tuxmaster5000 tuxmaster5000 added the bug Something isn't working label Feb 9, 2023
@nichtsfrei nichtsfrei mentioned this issue Feb 9, 2023
Merged
nichtsfrei added a commit to greenbone/gvm-libs that referenced this issue Feb 9, 2023
@nichtsfrei
Fix: set reference to volatile
f850e01 
Sets reference in logging.c to volatile to prevent wrongful compiler
optimizations on initialization.

This is an attempt to fix: greenbone/gsad#115
@nichtsfrei
Copy link
Member

nichtsfrei commented Feb 9, 2023 •
edited

We are unsure why: can you try to compile gvm libs with that https://github.com/greenbone/gvm-libs/pull/737/files patch?

nichtsfrei added a commit to greenbone/gvm-libs that referenced this issue Feb 9, 2023
@nichtsfrei
Fix: set reference to volatile
7158f5a 
Sets reference in logging.c to volatile to prevent wrongful compiler
optimizations on initialization.

This is an attempt to fix: greenbone/gsad#115
nichtsfrei added a commit to greenbone/gvm-libs that referenced this issue Feb 9, 2023
@nichtsfrei
Fix: set reference to volatile
9a28ac3 
Sets reference in logging.c to volatile to prevent wrongful compiler
optimizations on initialization.

This is an attempt to fix: greenbone/gsad#115
Kraemii pushed a commit to greenbone/gvm-libs that referenced this issue Feb 9, 2023
@nichtsfrei @Kraemii
Fix: set reference to static
d036a41 
Sets reference in logging.c to static to prevent wrongful compiler
optimizations on initialization.

This is an attempt to fix: greenbone/gsad#115
@bjoernricks
Copy link
Member

for me greenbone/gvm-libs#737 fixes the issue

nichtsfrei added a commit to greenbone/gvm-libs that referenced this issue Feb 9, 2023
@nichtsfrei
Fix: set reference to static
573ec74 
Sets reference in logging.c to static to prevent wrongful compiler
optimizations on initialization.

This is an attempt to fix: greenbone/gsad#115
mergify bot pushed a commit to greenbone/gvm-libs that referenced this issue Feb 9, 2023
@nichtsfrei @mergify
Fix: set reference to static
a24c924 
Sets reference in logging.c to static to prevent wrongful compiler
optimizations on initialization.

This is an attempt to fix: greenbone/gsad#115

(cherry picked from commit 573ec74)
Kraemii pushed a commit to greenbone/gvm-libs that referenced this issue Feb 9, 2023
@nichtsfrei @Kraemii
Fix: set reference to static
a97a53a 
Sets reference in logging.c to static to prevent wrongful compiler
optimizations on initialization.

This is an attempt to fix: greenbone/gsad#115

(cherry picked from commit 573ec74)
@tuxmaster5000
Copy link
Author

Yes it will also work on my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: set reference to static greenbone/gvm-libs
3 participants
@tuxmaster5000 @bjoernricks @nichtsfrei