Date: Thu, 24 Jan 2002 21:22:58 -0800 From: Peter Wemm <peter@wemm.org> To: Bernd Walter <ticso@cicely8.cicely.de> Cc: Wilko Bulte <wkb@freebie.xs4all.nl>, Andrew Gallatin <gallatin@cs.duke.edu>, Volker Stolz <stolz@hyperion.informatik.rwth-aachen.de>, freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/34232: rpc.statd throws alignment errors Message-ID: <20020125052258.534753BAB@overcee.wemm.org> In-Reply-To: <20020124221130.T75106@cicely8.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter wrote:
> On Thu, Jan 24, 2002 at 09:57:36PM +0100, Wilko Bulte wrote:
> > On Thu, Jan 24, 2002 at 03:51:27PM -0500, Andrew Gallatin wrote:
> > > Volker Stolz writes:
> > > > Am 24. Jan 2002 um 21:28 MET schrieb Andrew Gallatin:
> > > > > Volker Stolz writes:
> > > > > > bash$ gdb -c rpc.statd.core ./rpc.statd
> > > > > > This GDB was configured as "alpha-unknown-freebsd"...
> > > > > > Core was generated by `rpc.statd'.
> > > > > > Program terminated with signal 10, Bus error.
> > > > > > Reading symbols from /usr/lib/librpcsvc.so.2...done.
> > > > > > Reading symbols from /usr/lib/libc.so.4...done.
> > > > > > Reading symbols from /usr/libexec/ld-elf.so.1...done.
> > > > > > #0 0x1600bdf24 in get_myaddress () from /usr/lib/libc.so.4
> > > > > > (gdb)
> > > > >
> > > > > Closer. Now type "where" to get a stack trace.
> > > >
> > > > Nothing new:
> > > > (gdb) where
> > > > #0 0x1600bdf24 in get_myaddress () from /usr/lib/libc.so.4
> > > > warning: Hit heuristic-fence-post without finding
> > > > warning: enclosing function for address 0x100000000
> > > > ...
> > >
> > > F*cking gdb is broken. Oh well.. You could try linking it
> > > statically.
> > >
> > > What kind of a amcihine do you have? I'm wondering if this is a gcc
> > > bug. Eg, if you have an ev56 or better & you rebuild libc with
> >
> > That was also the theory on the ifconfig alignment errors.
>
> The ifconfig thing is simply a programming error when transfering
> structures over sysctl.
> I already stated to provide a fix over the weekend.
> If I'm guessing right that get_myaddress() also reads the interface
> list this might have the same reason.
Can you be a little more specific? Is the kernel generating an unaligned
sysctl data buffer?
I've also noticed that it only seems to happen for lo0.
peter@axp0[9:09pm]~-12# ifconfig dc0
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 216.136.204.64 netmask 0xffffff80 broadcast 216.136.204.127
ether 00:00:f8:75:92:0b
media: Ethernet 100baseTX <full-duplex>
status: active
peter@axp0[9:19pm]~-14# ifconfig lo0
pid 67706 (ifconfig): unaligned access: va=0x12006c13c pc=0x12000227c ra=0x120002270 op=ldq
pid 67706 (ifconfig): unaligned access: va=0x12006c134 pc=0x120002298 ra=0x120002270 op=ldq
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
I'm betting that get_myaddress() is running into the same problem. I seem
to remember this hitting the ia64 port as well but I am not certain.
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020125052258.534753BAB>