-
Notifications
You must be signed in to change notification settings - Fork 6
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
[23.10] Segmentation Fault in cbd Due to Null Pointer Dereference and Invalid Mutex Operation #1190
Comments
tphakala
changed the title
Segmentation Fault in cbd Due to Null Pointer Dereference and Invalid Mutex Operation
[23.10] Segmentation Fault in cbd Due to Null Pointer Dereference and Invalid Mutex Operation
Mar 6, 2024
Still happening with centreon-broker-cbd-23.10.5-1.el9.x86_64 |
kduret
pushed a commit
that referenced
this issue
Jun 24, 2024
kduret
pushed a commit
that referenced
this issue
Jul 10, 2024
kduret
pushed a commit
that referenced
this issue
Jul 10, 2024
kduret
pushed a commit
that referenced
this issue
Jul 11, 2024
Evan-Adam
pushed a commit
that referenced
this issue
Jul 16, 2024
kduret
pushed a commit
that referenced
this issue
Jul 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BUG REPORT INFORMATION
Prerequisites
Versions
Operating System
Red Hat Enterprise Linux release 9.3 (Plow)
How the the component has been installed and versions
Version: --
Additional environment details (AWS, VirtualBox, physical, etc.):
VMware vSphere virtual machine
Description
CBD crashes on reload
We have encountered a consistent segmentation fault across multiple instances of the cbd process, as evidenced by analysis of various core dumps generated by the application. The fault appears to be triggered during mutex lock operations within the threading and synchronization logic of the application. Below are the key observations from the gdb backtrace analysis of the core dumps:
Crash Context: The segmentation fault occurs at the point of attempting to lock a mutex (pthread_mutex_lock@@GLIBC_2.2.5) within the GNU C Library (libc.so.6).
Invalid Mutex Reference: The mutex operation attempts to lock a mutex at an invalid memory address (this=0x1b8). Such an address is highly indicative of a corrupted, uninitialized, or otherwise invalid mutex object, pointing towards a problem with the management of synchronization primitives in the application.
Null Pointer Dereference: The backtrace reveals that the crash happens during a call to com::centreon::broker::multiplexing::muxer::publish with a this pointer being null (this=this@entry=0x0). This indicates a scenario where the application attempts to access a member function of a class through a null pointer, leading to undefined behavior and, ultimately, a segmentation fault.
Recurring Pattern: The same pattern of crash is observed across different core dumps, suggesting a systematic issue with the application's handling of threading and synchronization, particularly regarding the lifecycle and integrity of muxer objects and associated mutexes.
Thread Safety Concerns: The crashes are related to threading operations, indicating potential issues with the thread safety of operations involving muxer objects or related synchronization mechanisms.
Steps to Reproduce
Export poller configuration from Central
Describe the received result
Some times cbd process crashes on segfault
Describe the expected result
cbd process should not crash on segfault
Logs
gdb backtrace
The text was updated successfully, but these errors were encountered: