Which distro are you running? For me, a debug flag didn't be stripped on my
RedHat 4.
Cheers,
--Nakarin
On Feb 25, 2010, at 1:09 PM, Jesse Becker wrote:
> On Thu, Feb 25, 2010 at 12:39:33AM -0500, Mark Burgess wrote:
>>
>> Jesse - can you please compile with debugging symbols -g so that the
>> backtrace shows some
>> details?
>
> Yep, that's on my list for today.
>
> Perhaps the RPMs could have the debugging information left in place?
> The gain from stripping them out should be modest, at the very best.
>
> Adding this line to the .spec file should do the trick:
>
> %define debug_package %{nil}
>
> Alternately, when creating the existing .rpm files, the build system
> should have created a -debuginfo package as well. Could you post those
> in the future (along with the src.rpm files as well)?
>
>
>>
>> M
>>
>> Jesse Becker wrote:
>>> I'm getting another segfault when running cf-agent, but it is not always
>>> reproducable. Given two runs back-to-back with no config file changes
>>> between, the first may fail, but the second will succeed. I don't think
>>> that I've seen two failures in a row of this nature.
>>>
>>> I'm running the RPM community binaries:
>>>
>>> # cf-agent -V
>>> This comprises cf-agent core community version 3.0.3patch1 - (C) Cfengine
>>> AS 2008-
>>>
>>> Here's the end of the verbose output, when run in gdb:
>>>
>>> <...snip...>
>>> cf3 *****************************************************************
>>> cf3 BUNDLE sge
>>> cf3 *****************************************************************
>>> cf3
>>> cf3
>>> cf3 =========================================================
>>> cf3 vars in bundle sge (1)
>>> cf3 =========================================================
>>> cf3
>>> cf3 Verifying SQL table promises is only available with Cfengine Nova or
>>> above
>>> cf3
>>> cf3 =========================================================
>>> cf3 classes in bundle sge (1)
>>> cf3 =========================================================
>>> cf3
>>> cf3 Verifying SQL table promises is only available with Cfengine Nova or
>>> above
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x000000000043dcbd in CompareVariable ()
>>> (gdb) bt
>>> #0 0x000000000043dcbd in CompareVariable ()
>>> #1 0x000000000043e022 in GetVariable ()
>>> #2 0x0000000000449745 in CopyRvalItem ()
>>> #3 0x0000000000447275 in DeRefCopyPromise ()
>>> #4 0x0000000000442279 in ExpandPromise ()
>>> #5 0x0000000000404cad in ScheduleAgentOperations ()
>>> #6 0x0000000000404e73 in KeepPromiseBundles ()
>>> #7 0x0000000000405983 in KeepPromises ()
>>> #8 0x0000000000405e9d in main ()
>>>
>>>
>>> I have *never* seen it coredump when I run with "-d 0", but I did (once)
>>> see a line after the "SQL tables promises" output that had what looked
>>> to be bogus output in it (e.g. a bad pointer somewhere for a printf).
>>>
>>> I am running using a specific set of bundles from a few files--I'll try
>>> to pare it down a bit to a specific test-case though.
>>>
>>>
>>>
>>
>> --
>> Mark Burgess
>>
>> -------------------------------------------------
>> Professor of Network and System Administration
>> Oslo University College, Norway
>>
>> Personal Web: http://www.iu.hio.no/~mark
>> Office Telf : +47 22453272
>> -------------------------------------------------
>
> --
> Jesse Becker
> NHGRI Linux support (Digicon Contractor)
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@cfengine.org
> https://cfengine.org/mailman/listinfo/help-cfengine
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
