Tuesday, February 6, 2024

[SOLVED] Geting SIGBUS (Bus error) @ 0 (0)killed by SIGBUS (core dumped) in Redhat

Issue

I have process that works perfectly in the same machine in 2 accounts but when i copy the process to other account and run the process im getting core dump. when i run the process with strace in the end im getting :

--- SIGBUS (Bus error) @ 0 (0) --- +++ killed by SIGBUS (core dumped) +++

when i open the core dump im getting :

#0  0x000000360046fed3 in malloc_consolidate () from /lib64/libc.so.6
#1  0x00000036004723fd in _int_malloc () from /lib64/libc.so.6
#2  0x000000360047402a in malloc () from /lib64/libc.so.6
#3  0x00000036004616ba in __fopen_internal () from /lib64/libc.so.6
#4  0x0000000000fe9652 in LogMngr::OpenFile (this=0x2aaaaad17010, iLogIndex=0) at LogMngr.c:801

i can see it something with opening the file for logging , but why it only in one account and in the other is fine ?


Solution

You can get a SIGBUS from an unaligned memory access . Are you using something like mmap, shared memory regions, or something similar ?



Answered By - Sandeep Pathak
Answer Checked By - Terry (WPSolving Volunteer)
at