Forum: CFEngine Help
Subject: Re: cf-agent 3.3.0 segmentation violation
Author: davidlee
Link to topic: https://cfengine.com/forum/read.php?3,25804,25815#msg-25815
This raises a wider problem, about the capability (or lack) of the cfengine
release management process to react to serious bugs in a
On 05/02/2012 10:47 PM, Taj Khattra wrote:
> platform: rhel 5 (2.6.18-194.el5), cfengine-community-3.3.0-1.x86_64.rpm
>
> the bundle below triggers a sigsegv in cf-agent.
> gdb stack trace indicates that strcmp() was called with a null first
> argument (logname) by SummarizeTransaction().
Yep. Ple
On Wed, May 2, 2012 at 4:03 PM, Neil Watson wrote:
> I'm no C hacker but I've seen seg faults too with 3.3. Might be related
> Bug report:
> https://cfengine.com/bugtracker/view.php?id=1089
i don't think they're related - i saw this with cfengine-3.2.1 too.
_
I'm no C hacker but I've seen seg faults too with 3.3. Might be related
Bug report:
https://cfengine.com/bugtracker/view.php?id=1089
--
Neil Watson
Linux/UNIX Consultant
http://watson-wilson.ca
___
Help-cfengine mailing list
Help-cfengine@cfengine.org
h
platform: rhel 5 (2.6.18-194.el5), cfengine-community-3.3.0-1.x86_64.rpm
the bundle below triggers a sigsegv in cf-agent.
gdb stack trace indicates that strcmp() was called with a null first
argument (logname) by SummarizeTransaction().
thanks
-taj
core.cf
body common control
{
bundle
