thx for alerting, I'll check what is/was going on. Rainer
El vie, 12 dic 2025 a las 22:05, Julien Thomas (<[email protected]>) escribió: > > Hello Rainer, > > On 05/12/2025 09:12, Rainer Gerhards via rsyslog wrote: > > [...] > > > > This version addresses two specific issues: a potential segmentation > > fault occurring on specific platforms and a memory leak related to > > custom type mismatches in rules. > > > > [...] > Unfortunately Meric's patch, fixing memory leak when a custom type in > rules does not match, was not included in liblognorm 2.0.8 release. > There was most likely a merge issue with rsyslog/liblognorm#380. > > Both the release tarball and the sources from tag v2.0.8 were tested. > None include the patch: > http://www.liblognorm.com/files/download/liblognorm-2.0.8.tar.gz > https://github.com/rsyslog/liblognorm/archive/refs/tags/v2.0.8.tar.gz > > Tag rsyslog/[email protected] on commit rsyslog/liblognorm@33ec4b0 does > not include the patch rsyslog/liblognorm@1fc4f689 from pull request > rsyslog/liblognorm#380. > > The patch is NOT included either in current master HEAD > rsyslog/liblognorm@3580c9b. However it is included in current stable > HEAD rsyslog/liblognorm@15f2d22. > > Could you have a look and release a 2.0.9 version of liblognorm? > > Cheers, > Julien _______________________________________________ rsyslog mailing list https://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.
