Re: netstat segv in current/amd64

[Paul Goyette <paul%whooppee.com@localhost>]

Happens on my 5.99.51 system built from sources on 2011-05-08 at 
14:01:18 UTC ...

In my case, my kernel has no IPv6 support.  Here's what I get:

{140} netstat
Active Internet connections
Proto Recv-Q Send-Q  Local Address          Foreign Address        State
tcp        0      0  screamer.51413         morden.netbsd.or.60949 TIME_WAIT
tcp        0      0  screamer.51413         morden.netbsd.or.60968 ESTABLISHED
tcp      128      0  screamer.59500         quicky.x11             ESTABLISHED
tcp        0      0  screamer.59504         quicky.x11             ESTABLISHED
tcp        0      0  screamer.ssh           quicky.65522           ESTABLISHED
Segmentation fault
{141}

On Tue, 10 May 2011, Gary Duzan wrote:

>   After a recent upgrade of current (full upgrade via installer),
> running netstat with no arguments results in a segmentation fault.
> If I run with "-f inet" or "-f inet6", I get reasonable looking
> results, then the segmentation fault. From the ktrace it looks like
> it is reading through /dev/kmem just before the crash, and gdb (on
> a standard non-debug binary) shows the following:
>
> ###########################################################################
> brain { ~ } # gdb `which netstat`
> GNU gdb 6.5
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "x86_64--netbsd"...(no debugging symbols found)
>
> (gdb) run -f inet
> Starting program: /usr/bin/netstat -f inet
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000408ca3 in print_vtw_v4 ()
> (gdb) where
> #0  0x0000000000408ca3 in print_vtw_v4 ()
> #1  0x0000000000414753 in process_vtw ()
> #2  0x0000000000414c9c in show_vtw_v4 ()
> #3  0x00000000004093d0 in protopr ()
> #4  0x00000000004106b0 in main ()
> (gdb)
> ###########################################################################
>
>   In other tests I've had gdb hang while trying to debug netstat,
> and I was a bit surprised to get this stack trace.
>
>   Has anyone else seen this? Thanks.
>
>                                         Gary Duzan
>
>
>
> !DSPAM:4dc959882401093577884!

-------------------------------------------------------------------------
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------