[Lognorm] Memory Leak in liblognorm?

[Champ Clark III]

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

I know you are a busy guy,  so no rush :)

>>> well, es_newStr() is like malloc.
>> so
> 
>> char *s; s=malloc(); s=malloc(); free(s);
> 
>> creates a leak. You must free the str object before the ptr is
>> overwritten. Does that help?


Well, not really.

I call "es_newStrFromCStr" one time,  and then call
"es_deleteStr(str);" one time (at the end).   So I don't think the
malloc example applies.

I'll keep plugging away at it.


- -- 
- - 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 Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJR5By5AAoJENnmXt7Lmc3KXO0H/0FqRj13KFdFjf18DddGJ6RD
gyH0NxNwMkFmBEhi3lXj7AyVAq2+UxinqXAAYwE53qCqiELCoDwY4D3zjv84aRsD
wZIGsQDmtWLZ60vY/wFZRFGFxZxXySxJ3czNmGPON7R1nKzxXsaKQQu9rej5B+BW
Bh2TFWqcva29UAko+Rfx5hMAOanDUf0l3trWOf5VRCk9VTP+e4cMIHT3DkToXTc/
5AIa2AgMQYR0lOb02qQAKbYCSVvLQDnBWn7fYanNbLNB4+Vysa8MKdVvmXy8Yd1B
YSyUzxPsOz7JYJD3WrDqONPnfiJEbRKW67mpqG0BLsb/k2qzQZ42HK+54mqOmqs=
=l+On
-----END PGP SIGNATURE-----