Hi, I am building an embedded system and I have a certain config which
is all working well, until I change and enable UCLIBC_USE_NETLINK=y and
UCLIBC_SUPPORT_AI_ADDRCONFIG=y in uclibc-0.30.1 config
As soon as I enable the second option then I start getting segfaults
whenever I run anything that tries to use the network (eg busybox ping,
dropbear, busybox telnet). ifconfig works fine, as does bringing up the
interface
The build environment is gentoo-hardened (gcc 3.4.6) with uclibc-0.30.1
and busybox 1.14.2. The build environment is a 32bit chroot on a 64bit
kernel. The target machine is an x86 alix board
What is very odd is that if I chroot into the build on the build machine
then ping, etc works fine. However, with a different kernel (but very
similar) on the alix board I get these segfaults. I have switched the
target to a 2.6.29.6 vanilla kernel to try and eliminate that - the
build machine is running 2.6.29.6 64bit with some patches (hardened+vserver)
Obviously it's going to be a pain to turn on symbols and try to get a
backtrace on the embedded board, so hoping someone has some other ideas?
Grateful for any thoughts?
Ed W
_______________________________________________
uClibc mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/uclibc
