Package: libspf2-2
Version: 1.2.5.dfsg-4
Severity: important
I am experiencing problems with libspf2. I have been trying various
versions starting with libspf2 1.0.4, and so far every version I tried
(up to the debian libspf 1.2.5.dfsg-4) is having the same problems.
In this case I'm trying with libspf 1.2.5.dfsg-4 (debian).
I am using this library like this:
SPF_server_t *spf_server = SPF_server_new(SPF_DNS_CACHE, 0);
SPF_request_t *spf_request = SPF_request_new(spf_server);
SPF_response_t *spf_response = NULL;
But as soon as I initialize the server, memory gets corrupted:
[PC: 0xb7d478cc] (Thread 0) **FREE_NULL**
Freeing null pointer.
Stack trace where the error occurred:
realloc() (interface)
SPF_record_compile_macro()
SPF_record_compile()
SPF_server_set_localpolicy()
SPF_server_new()
main() autoreply.c, 116
**Memory corrupted. Program may crash!!**
The above dump is from the binary debian package, below is the dump from
the (debian) source package:
[spf_compile.c:107] (Thread 0) **FREE_NULL**
>> *datap = realloc(*datap, size);
Freeing null pointer: *datap
Stack trace where the error occurred:
SPF_c_ensure_capacity() spf_compile.c, 107
SPF_c_mech_add() spf_compile.c, 831
SPF_record_compile() spf_compile.c, 1260
SPF_server_set_localpolicy() spf_server.c, 226
SPF_server_new() spf_server.c, 127
main() autoreply.c, 116
**Memory corrupted. Program may crash!!**
Most of the times my program survives, but sometimes my program does
indeed crash after it does some memory operations, so I have the feeling
my code checker (Insure++) is right and libspf2 is indeed trying to free
a null pointer.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686-bigmem
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages libspf2-2 depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
libspf2-2 recommends no packages.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
