ndt-users list created

Linux: 2.6.28.10-web100
libpcap: 1.0.0
NDT: 3.5.0

During test, I'm getting a Signal 11 (SIGSEGV).  I've seen this reported in 
other posts here, as well, related to "Protocol error!" and "C2S throughput 
test FAILED!" messages in the log.

Is this normal?  I would think a SIGSEGV would never be genuinely "normal."

Stack trace captured from fault via GDB (note: line numbers are close, but 
not exact to unaltered web100srv.c since I added a few lines of logging and a 
sleep in order to attach to the running child process):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208669888 (LWP 3315)]
0x080703cb in pcap_read_linux_mmap (handle=0x80aba18, max_packets=-1, 
callback=0x8053010 <print_speed>,
    user=0xbf861f7c "\206á") at ./pcap-linux.c:2143
2143            h.raw = RING_GET_FRAME(handle);
(gdb) where
#0  0x080703cb in pcap_read_linux_mmap (handle=0x80aba18, max_packets=-1, 
callback=0x8053010 <print_speed>,
    user=0xbf861f7c "\206á") at ./pcap-linux.c:2143
#1  0x0805c97b in pcap_loop ()
#2  0x08051e27 in init_pkttrace (sock_addr=0xbf861eb4, saddrlen=16, 
monitor_pipe=0x80a1ce8, device=0x0,
    pair=0xbf861f7c) at web100-pcap.c:650
#3  0x080593cc in test_c2s (ctlsockfd=4, agent=0x80a3db0, 
testOptions=0xbf863ac8, conn_options=2,
    c2sspd=0xbf8639e0, set_buff=0, window=64000, autotune=22, device=0x0, 
options=0x808f560,
    record_reverse=0, count_vars=69, spds=0xbf863568, spd_index=0xbf863a08) 
at testoptions.c:495
#4  0x0804ac88 in run_test (agent=0x80a3db0, ctlsockfd=4, testopt=
      {multiple = 1, mainport = 0, midopt = 1, midsockfd = 5, midsockport = 
57337, c2sopt = 1, c2ssockfd = 5, c2ssockport = 57734, s2copt = 1, s2csockfd 
= 0, s2csockport = 0, sfwopt = 1}) at web100srv.c:696
#5  0x0804e87c in main (argc=7, argv=0xbf8642b4) at web100srv.c:1635