[Lognorm] Is liblognorm ( libee, libestr, etc) thread safe?

[Champ Clark III]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That Rainer,

I'm keeping the construction phase separate/isolated.   I think I'm
good there.  I made some modification to the code and it's been
running for the last 15 or so hours.   I can reproduce the issue in
certain situations,  but I think this is something wrong with my code.

Thanks for the quick answer and pointers.

On 5/5/12 4:38 AM, Rainer Gerhards wrote:
>> Does anyone know if liblognorm (and the associated libs) are 
>> considered "thread" safe.  I need to move some normalization to
>> a pthread,  and was just curious.   Any pointers would be great.
> 
> It is not thread-safe during the construction phase (sample db
> loading, parsing of the message), but otherwise should be.
> 
> To diagnose, can you give it a try with valgrind's helgrind AND drd
> tools (use both as they have different strengths and problems ;)) ?
> That should bring up issues...
> 
> Rainer _______________________________________________ Lognorm
> mailing list Lognorm at lists.adiscon.com 
> http://lists.adiscon.net/mailman/listinfo/lognorm


- -- 
- - Champ Clark III (cclark at quadrantsec.com)
  Quadrant Information Security (http://quadrantsec.com)
  Key Fingerprint: 2E56 C2EB 1B25 C517 D5BA 2DCF 5E70 B2F8 0381 878A
  GPG Key ID: 0381878A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPpU5HAAoJENnmXt7Lmc3K+xEH/3qT06/sL2CRANJ90OMf+Uzk
QmRXCrR5aHHfR8GlMwah6zTS7Ao6dcT99+/KAb+NoCHOL3fnPIaXFigVuLOn/yA/
Xw6RC7mXPkelIhjD2BSa0BxGs84w3sez6oYtzFzee3rZwl1gxmAs3zz110+xKkpg
/cTa9Qdl/URGkj1BCA3Vtz4dCgodk4qMwqj9pf+m/H37HG4UXJlsylcV22yzLuPJ
lepNMUc5w+V5yOATzrfg6B/AGreHEW40iPeVqRY3q7PLnA2TZHxkqFzbohLU8ChA
SWMfPkcZXO8ODckv4GwKhpJflFZNGyL+A76Ok83WG7TsNALQt2eAZxaQmHf6vH0=
=Fe6k
-----END PGP SIGNATURE-----