[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: busybox 1.5.1 syslogd segfaults?
From:       Denis Vlasenko <vda.linux () googlemail ! com>
Date:       2007-05-26 16:21:50
Message-ID: 200705261821.51003.vda.linux () googlemail ! com
[Download RAW message or body]

On Thursday 24 May 2007 02:59, Clem Taylor wrote:
> Has anyone else tried 1.5.1 syslogd? I just tried switching over to
> busybox 1.5.1 from a 20070312 snapshot and found that syslogd was
> segfaulting. I normally run syslog with something like:
> syslogd -m 0 -R 192.168.50.49  -L -S -C64
> 
> I need to rebuild with debugging turned on, because running gdb on
> busybox_unstripped just says that it is segfaulting in syslogd_main().
> 
> Has anyone else tried out the 1.5.1 syslogd?
> 
> I have the following syslog options enabled:
> CONFIG_FEATURE_SYSLOG=y
> CONFIG_FEATURE_INIT_SYSLOG=y
> CONFIG_FEATURE_SU_SYSLOG=y
> CONFIG_FEATURE_UDHCP_SYSLOG=y
> CONFIG_SYSLOGD=y
> CONFIG_FEATURE_REMOTE_LOG=y
> CONFIG_FEATURE_IPC_SYSLOG=y
> CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE=64
> CONFIG_LOGREAD=y
> CONFIG_FEATURE_LOGREAD_REDUCED_LOCKING=y
> CONFIG_KLOGD=y
> CONFIG_LOGGER=y
> 
> I'm using mipsel gcc 3.4.6 with uClibc-0.9.28.2...

Current svn busybox compiled for i386, gcc 4.1.2, glibc
works for me (I added -n option):

# strace -tt -o zz /usr/srcdevel/bbox/fix/busybox.t2/busybox syslogd -m 0 -R \
192.168.50.49 -L -S -C64   -n

On another console

# logger <klogd.c

Strace log is attached.
--
vda


["zz.bz2" (application/x-bzip2)]

_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox

[prev in list] [next in list] [prev in thread] [next in thread]