Wind River Support Network

HomeDefectsLIN6-13352
Fixed

LIN6-13352 : rsyslogd is coring.

Created: Aug 3, 2017    Updated: Dec 3, 2018
Resolved Date: Sep 24, 2017
Found In Version: 6.0.0.18
Fix Version: 6.0.0.35
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Build & Config

Description

Customer is getting an error  with rsyslogd that is crashing with a segmentation fault. He claims the error was fixed with commit 6d258339802cb9f13d8a4a157a4b74eccb902d8f   from git repository  https://github.com/rsyslog/rsyslog/issues/1573   

I was checking for related Jiras about this error and I was not able to found any entry.  Is it possible to include this patch to Linux 6 ?



root@fpc0:/tmp# gdb ./rsyslogd imuxsock.core GNU gdb (Wind River Linux Sourcery CodeBench 4.8-42) 7.6 ... 
[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". 
Core was generated by `/usr/sbin/rsyslogd'. 
Program terminated with signal 11, Segmentation fault. 
#0 __GI___pthread_mutex_lock (mutex=mutex@entry=0x20) at pthread_mutex_lock.c:66 
66 pthread_mutex_lock.c: No such file or directory. 
(gdb) bt 
#0 __GI___pthread_mutex_lock (mutex=mutex@entry=0x20) at pthread_mutex_lock.c:66 
#1 0x10050be8 in AddRef (pThis=0x0) at prop.c:135 
#2 0x100323b0 in MsgSetRcvFrom (pThis=0xf5b18250, new=<optimized out>) at msg.c:2256 
#3 0x0fa83d8c in ?? () from /usr/lib/rsyslog/imuxsock.so 
#4 0x0fa8483c in ?? () from /usr/lib/rsyslog/imuxsock.so 
#5 0x10059578 in thrdStarter (arg=0xf5b18250) at ../threads.c:212 
#6 0x0fdd7dfc in start_thread (arg=0xf76c8480) at pthread_create.c:314 
#7 0x0ff193c0 in clone () from /lib/libc.so.6 



Other Downloads


Live chat
Online