Hi Folks, I am seeing the following stack trace with a SEGV (filed as BZ https://bugzilla.redhat.com/show_bug.cgi?id=1549706):
(gdb) where #0 rsCStrDestruct (ppThis=ppThis@entry=0x7ffed00168f0) at stringbuf.c:216 #1 0x000055555558a468 in varDestruct (ppThis=0x7ffed86d1bc0) at var.c:72 #2 0x0000555555576314 in MsgDeserialize (pMsg=0x7ffed0019680, pStrm=pStrm@entry=0x555555826ed0) at msg.c:1405 #3 0x00005555555822a9 in objDeserializeWithMethods (ppObj=0x7ffed86d1cf0, pszTypeExpected=pszTypeExpected@entry=0x5555555bbfe6 "msg", lenTypeExpected=lenTypeExpected@entry=3, pStrm=0x555555826ed0, fFixup=fFixup@entry=0x0, pUsr=pUsr@entry=0x0, objConstruct=0x555555574100 <msgConstructForDeserializer>, objConstructFinalize=objConstructFinalize@entry=0x0, objDeserialize=0x5555555762b0 <MsgDeserialize>) at obj.c:915 #4 0x000055555558c8b8 in qDeqDisk (pThis=<optimized out>, ppMsg=<optimized out>) at queue.c:988 #5 0x000055555558e741 in qqueueDeq (ppMsg=0x7ffed86d1cf0, pThis=0x555555823080) at queue.c:1115 #6 DequeueConsumableElements (pSkippedMsgs=<optimized out>, piRemainingQueueSize=<synthetic pointer>, pWti=<optimized out>, pThis=0x555555823080) at queue.c:1713 #7 DequeueConsumable (pThis=pThis@entry=0x555555823080, pWti=pWti@entry=0x5555558235d0, pSkippedMsgs=pSkippedMsgs@entry=0x7ffed86d1d44) at queue.c:1767 #8 0x000055555558ea92 in DequeueForConsumer (pSkippedMsgs=0x7ffed86d1d44, pWti=0x5555558235d0, pThis=0x555555823080) at queue.c:1919 #9 ConsumerReg (pThis=0x555555823080, pWti=0x5555558235d0) at queue.c:1975 #10 0x000055555558b66e in wtiWorker (pThis=pThis@entry=0x5555558235d0) at wti.c:365 #11 0x000055555558a7dd in wtpWorker (arg=0x5555558235d0) at wtp.c:410 #12 0x00007ffff79b0e25 in start_thread (arg=0x7ffed86d2700) at pthread_create.c:308 #13 0x00007ffff6aa934d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 I saw a similar stack trace from long ago, but would guess it is not the same thing: https://access.redhat.com/solutions/882893 Does it look familiar to anybody? I have this in a reproducible fashion today on two different systems, thinking it is a corrupted queue file. Thanks, -peter _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
