Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Jun 2023 09:53:50 +0000
From:      Gary Jennejohn <garyj@gmx.de>
To:        Alexander Chernikov <melifaro@FreeBSD.org>
Cc:        current@freebsd.org
Subject:   Re: ifconfig dumps core and gdb uses an undefined symbol
Message-ID:  <20230614115350.5e7386fa@ernst.home>
In-Reply-To: <20230614110135.15b928db@ernst.home>
References:  <20230614095956.26234554@ernst.home> <7A98AD66-35D3-447B-B808-2A52E9AD28F3@FreeBSD.org> <20230614110135.15b928db@ernst.home>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 14 Jun 2023 09:01:35 +0000
Gary Jennejohn <garyj@gmx.de> wrote:

> On Wed, 14 Jun 2023 09:09:04 +0100
> Alexander Chernikov <melifaro@FreeBSD.org> wrote:
>
> > > On 14 Jun 2023, at 08:59, Gary Jennejohn <garyj@gmx.de> wrote:
> > Hi Gary,
> > >
> > > So, now I have a new problem with current.
> > >
> > > I just now updated my current sources and ran buildworld and buildke=
rnel,
> > > since Gleb fixed the WITHOUT_PF problem.
> > >
> > > After installing the new world and kernel I see that ifconfig is dum=
ping
> > > a core, apparently when it tries to show lo0, since re0 is correctly
> > > shown:
> > >
> > > ifconfig
> > > re0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 m=
tu 4088 options=3D82098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINK=
STATE>
> > >       ether redacted
> > >       inet 192.168.178.XXX netmask 0xffffff00 broadcast 192.168.178.=
255
> > > Segmentation fault (core dumped)
> > Could you please try to narrow down the crashing command? e.g.
> > Ifconfig lo0
> > Ifconfig lo0 net
> > Ifconfig lo0 inet6
> > Could you try to rebuild ifconfig w/o netlink (e.g. set WITHOUT_NETLIN=
K=3Dyes in the make.conf & make -C sbin/ifconfig clean all install) and se=
e if the new binary works?
> >
>
> I already have WITHOUT_NETLINK=3Dyes in my /etc/src.conf.
>
> I didn't install ifconfig. I simply started it from the build directory.
>
> ifconfig lo0 shows the settings for lo0 and then dumps core.
>

After your most recent changes "ifconfig re0" and "ifconfg lo0" don't
result in any errors.  But "ifconfig" alone still results in a core
dump, which per gdb is happening in the strlcpy() call at in_status_tunnel=
()
in af_inet.c.

=2D-
Gary Jennejohn



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230614115350.5e7386fa>