Your message dated Thu, 7 Feb 2008 21:17:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [noop] iptables-dev: libiptc doesn't provide a way to
deallocate iptc_handle
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: iptables-dev
Version: 1.2.8-4
Severity: normal
libiptc seems to lack a way to rollback a transaction initiated with
iptc_init(). Once the memory is allocated, one cannot avoid a memory
leak (in a long-running program) unless they call iptc_commit()
succesfully.
In particular, if the table is changed by some other process in the
middle of iptc_init/iptc_commit transaction, iptc_commit seems to fail.
This is a guaranteed memory leak.
Providing an iptc_dealloc function would solve these problems.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux lunix 2.4.21-2-686 #1 Sat Jul 5 00:38:35 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages iptables-dev depends on:
ii iptables 1.2.8-4 IP packet filter administration to
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.4.0-1
libiptc was been withdrawn from the iptables-dev package
--- End Message ---
