core dumps with iptables v1.1.0

[Nicholas Dronen]

Hi, 

Since upgrading to iptables 1.1.0, I've been getting core dumps.
I tried using the cvs code last night but got the same results.

I'm running kernel version 2.4.0-test1.

Here's the stack trace.

$ gdb -q /usr/local/bin/iptables core
(no debugging symbols found)...
Core was generated by `iptables -D INPUT -m state --state NEW -i eth0 -j
DENY'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libdl.so.2...(no debugging symbols
found)...done.
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
found)...done.
Reading symbols from /usr/local/lib/iptables/libipt_state.so...(no
debugging symbols found)...
done.
#0  0x804b226 in make_delete_mask ()
(gdb) where
#0  0x804b226 in make_delete_mask ()
#1  0x804b2d8 in delete_entry ()
#2  0x804c8a9 in do_command ()
#3  0x804963a in main ()
#4  0x40036a42 in __libc_start_main () from /lib/libc.so.6

Since upgrading to 1.1.0 I've also started to get the following
errors (the lines beginning with a '+' are from my iptables
initialization script running set -x).

+ iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables: No extended target/match by that name
+ iptables -A INPUT -m state --state NEW -i eth0 -j DENY
iptables: No extended target/match by that name

Did something change between 1.0.0 and 1.1.0 that I missed?
iptables(8) still shouldn't dump core if it's given invalid
arguments, so this is part bug-report, part request for more
information.

Regards.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ nick dronen                (unsigned char *) "ndronen at frii dot com" +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++