[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with SEGV solved: do _not_ link statically ...

From: Mark . Burgess
Subject: Re: Problem with SEGV solved: do _not_ link statically ...
Date: Sat, 18 May 2002 10:24:48 +0200 (MET DST)

This sounds unlikely, but it might be that some static linking of the
BerkeleyDB library is causing the problem. When you delete the lock
database, cfengine will recreate it unless you use -K. Perhaps
that is the problem.

I don't know what to say/do about this. I have not tried static
linking myself. But if it's working with ldso ... then I think it
cannot be a cfengine problem.


On 13 May, Thomas Glanzmann wrote:
> On Mon, 13 May 2002, Thomas Glanzmann wrote:
> To run cfengine short (for debug purposes)
> I deleted /var/cfengine/*lock* ... then I think the segfault happened.
> If I use -K ... it doesn't ... I think that was all about that stupid thing.
> Could that be the reason?
>> Any ideas?
>> I tried to link cfengine statically and it had some Problems with lists ... 
>> eg
>> allocating and freeing memory ... If I compile it dynamically it works.
>> The problem occures with Linux ... I tried different gcc, linker and libc ...
>> The problem persists ... but it 'moves' from time to time (compiler).
>> Does anybody have a staically linked version for linux (2.0.1) running? Than
>> please send me a copy ... so that I can try that one on my site.
>> Thank ya.
>> --tg

Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark

reply via email to

[Prev in Thread] Current Thread [Next in Thread]