Further investigation reveals the cause:
DHCPD was manually configured, and did not contain an entry of the
form:
server-identifier xxxxx;
The lack of a "server-identifier" entry causes the segmentation
violation at line 899 of dhcpedit.cc.

Please note that this was not required for previous releases, and may
affect other users who are upgrading.

Also note that if multiple ranges for a subnet are specified, the
linuxconf program will only display the last one of the group. An
example of this would be:

subnet 192.168.1.1 netmask 255.255.255.0 {
    range 192.168.1.10 192.168.1.100;
    range 192.168.1.110 192.168.1.200;
}

which would only display the range 110-200.

-Rory

Linuxconf on a Toshiba 8000 laptop segfaults often, usually
when trying to "accept" a feature during networking setup.
It has segfaulted nearly 10 times as I have setup the RH6.0 laptop.

linuxconf also segfaults on my machine, even after reinstalling the
package.
1024 # linuxconf
Segmentation fault

linuxconf segfaults when launched, for me, too.  I'm running RHL6.0
(Intel) on a Pentium or PII.  DNS (resolver & BIND), IMAP, and
SendMail are the only network services.

Reported fixed in linuxconf-1.16r1.3, released as update RHEA-1999:026