Richard A Nelson <[EMAIL PROTECTED]> writes: >>> ==12662== Invalid read of size 1 >>> ==12662== at 0x80778C8: (within /usr/sbin/cfagent) >>> ==12662== by 0x8077A8A: (within /usr/sbin/cfagent) >>> ==12662== by 0x807A48E: (within /usr/sbin/cfagent) >>> ==12662== by 0x8053AC0: (within /usr/sbin/cfagent) >>> ==12662== by 0x8053ECC: (within /usr/sbin/cfagent) >>> ==12662== by 0x431A44F: (below main) (libc-start.c:222) >>> ==12662== Address 0x0 is not stack'd, malloc'd or (recently) free'd >>> ==12662== >>> ==12662== Process terminating with default action of signal 11 (SIGSEGV) >>> ==12662== Access not within mapped region at address 0x0 > >> Hi, >> >> and sorry for this late reply. Have you tested if this is improved >> with 2.2.7-1 of cfengine? > > I don't see it on the servers (amd64), but it persists on the > client (x86-32) boxen - now with about the same regularity (ie, not > every single run, but a couple times a day) - so much better than > before :)
Cfengine2 2.2.8-1 was uploaded to unstable a few days ago, are you able to test this version as well? Upstream claims that they have been "fixing an important threading error that has become apparent with the influx of multicore processors". - Werner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
