RE: Tracking Heap Corruption bug

I've broken my spf code out into a separate executable.  I've examined it with valgrind and I can't get it to do anything weird except the error message below.   I did get it to do something weird one time when I wasn't running valgrind.  I'm thinking that the spammers DNS is doing something weird intermittently.  Since I can't track down this heap corruption bug, and because it's too dangerous to let live, I'm just going to separate all the ospf calls out and my software and instead call a separate executable to do the checks.

root@davidsbox:/MyProjects/cipafilter# valgrind ./spf-helper 216.110.191.113 [email protected] r32586.willfindyourmatch.com; echo $?
==7227== Memcheck, a memory error detector.
==7227== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==7227== Using LibVEX rev 1732, a library for dynamic binary translation.
==7227== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==7227== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==7227== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==7227== For more details, rerun with: -v
==7227==
Using HELO domain: r32586.willfindyourmatch.com
Using from address: [email protected]
==7227== Conditional jump or move depends on uninitialised value(s)
==7227==    at 0x457AABB: __res_vinit (in /lib/libc-2.2.3.so)
==7227==    by 0x457A18F: __res_ninit (res_init.c:135)
==7227==    by 0x44884A1: SPF_dns_resolv_lookup (spf_dns_resolv.c:147)
==7227==    by 0x44877A2: SPF_dns_lookup (spf_dns.c:114)
==7227==    by 0x4487E71: SPF_dns_cache_lookup (spf_dns_cache.c:387)
==7227==    by 0x44877A2: SPF_dns_lookup (spf_dns.c:114)
==7227==    by 0x448F6FD: SPF_server_get_record (spf_server.c:275)
==7227==    by 0x448E8AB: SPF_request_query_mailfrom (spf_request.c:253)
==7227==    by 0x8048B7B: main (spf-helper.c:83)
Error: Unknown SPF Response: 0
Exteneded SPF Pass
==7227==
==7227== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 5 from 3)
==7227== malloc/free: in use at exit: 2,648 bytes in 27 blocks.
==7227== malloc/free: 62 allocs, 36 frees, 4,773 bytes allocated.
==7227== For counts of detected errors, rerun with: -v
==7227== searching for pointers to 27 not-freed blocks.
==7227== checked 320,800 bytes.
==7227==
==7227== LEAK SUMMARY:
==7227==    definitely lost: 0 bytes in 0 blocks.
==7227==      possibly lost: 0 bytes in 0 blocks.
==7227==    still reachable: 2,648 bytes in 27 blocks.
==7227==         suppressed: 0 bytes in 0 blocks.
==7227== Rerun with --leak-check=full to see details of leaked memory.
0



-----Original Message-----
From: Scott Kitterman [mailto:[email protected]]
Sent: Wed 9/12/2007 9:57 AM
To: [email protected]
Subject: RE: [spf-devel] Tracking Heap Corruption bug
 
Technically there is no reason why not.  The last libspf2 maintainer went 
MIA.  I'm working on talking someone else into it right now.

So I'd say eventually.

Scott K

On Wed, 12 Sep 2007 09:44:33 -0500 "David Hinkle" <[email protected]> 
wrote:
>Are these patches going into the main distribution?
>
>David
>
>
>-----Original Message-----
>From: Scott Kitterman [mailto:[email protected]]
>Sent: Wed 9/12/2007 5:42 AM
>To: [email protected]
>Subject: Re: [spf-devel] Tracking Heap Corruption bug
> 
>On Wed, 12 Sep 2007 11:48:26 +0200 Magnus Holmgren 
><[email protected]> wrote:
>>On Wednesday 12 September 2007 02:02, Scott Kitterman wrote:
>>> On Tuesday 11 September 2007 19:18, David Hinkle wrote:
>>> > Oh yea, libspf2.  Revision 1.2.5
>>>
>>> I'd suggest looking at the Debian package as it has some 64 bit related
>>> fixes. Do check each file as there is at least one patch in there that 
is
>>> GPL only (IIRC).
>>
>>No, I managed to persuade Robert.
>>
>Thanks for that.  I appreciate you making the effort to keep the Debian 
>licensing consistent with the original author's.
>
>Scott K
>
>-------------------------------------------
>-----------------------------------------------------------------------
>To unsubscribe, change your address, or temporarily deactivate your
>subscription,
>please go to http://v2.listbox.com/member/?&
>Powered by Listbox: http://www.listbox.com
>
>-------------------------------------------
>-----------------------------------------------------------------------
>To unsubscribe, change your address, or temporarily deactivate your
>subscription,
>please go to http://v2.listbox.com/member/?&
>Powered by Listbox: http://www.listbox.com
>

-------------------------------------------
-----------------------------------------------------------------------
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to http://v2.listbox.com/member/?&
Powered by Listbox: http://www.listbox.com

-------------------------------------------
-----------------------------------------------------------------------
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to http://v2.listbox.com/member/?member_id=6959932&id_secret=41000915-da2f14
Powered by Listbox: http://www.listbox.com