I found it, a dumb mistake probably rooted in year-long training with zero-terminated strings ;)
fix: http://git.adiscon.com/?p=liblognorm.git;a=commit;h=c36358fb071f269b54e3b8891 f300ee15a231eb3 It crashed iff a log prefix for a node was generated with *exactly* 16 bytes of size. Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Champ Clark III [Softwink] > Sent: Monday, January 10, 2011 7:09 PM > To: rsyslog-users > Subject: Re: [rsyslog] Strange liblognorm issue(s)... > > On Mon, Jan 10, 2011 at 06:57:00PM +0100, Rainer Gerhards wrote: > > I couldn't stand it, copied & pasted the info. Same segfault here :) > valgrind > > tells me it is ptree.c/627 (628 if you remove the comment). This is > inside > > the parse tree as expected. Let me see if I find out tomorrow what > goes on. > > No rush. Just wanting to point it out as I ran into it > yesterday. It was driving me nuts :) > > -- > Champ Clark III | Softwink, Inc | 800-538-9357 x 101 > http://www.softwink.com > > GPG Key ID: 58A2A58F > Key fingerprint = 7734 2A1C 007D 581E BDF7 6AD5 0F1F 655F 58A2 A58F > If it wasn't for C, we'd be using BASI, PASAL and OBOL. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
