>Number:         7062
>Category:       bin
>Synopsis:       syslogd dumps core after receiving remote message
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 28 02:35:00 1999
>Last-Modified:
>Originator:     Matthias Scheler
>Organization:
Matthias Scheler                                http://home.owl.de/~tron/
>Release:        19990227
>Environment:
System: NetBSD lyssa.owl.de 1.3J NetBSD 1.3J (LYSSA) #1: Sun Feb 28 00:48:09 MET 1999 tron@lyssa.owl.de:/src/sys/compile/LYSSA i386

>Description:
Recently I discovered that the "syslogd" on my current system wasn't running.
I restarted it but a few minutes later it was down again. After debugging
it with "gdb" I found that it crashes on the first message from a remote
system in malloc() while doing gethostbyname(). Obviously something is
broken in the dynamic argument array handling which cause the memory list
to be corrupted.

>How-To-Repeat:
Watch "syslogd" on a system which receives remote messages.

>Fix:
Back out revision 1.22.
>Audit-Trail:
>Unformatted: