recent libc's syslog changes break my amd64 system startup

[Markus W Kilbinger <mk%kilbi.de@localhost>]

Hi!

Since

  http://mail-index.netbsd.org/source-changes/2008/10/31/msg212068.html

my amd64 machine is no longer capable to start up cleanly because many
programs during booting dump core, all with the same bt, e. g.:

  # gdb /usr/sbin/rpcbind /rpcbind.core                                         
            
  GNU gdb 6.5
  Copyright (C) 2006 Free Software Foundation, Inc.
  GDB is free software, covered by the GNU General Public License, and you are
  welcome to change it and/or distribute copies of it under certain conditions.
  Type "show copying" to see the conditions.
  There is absolutely no warranty for GDB.  Type "show warranty" for details.
  This GDB was configured as "x86_64--netbsd"...(no debugging symbols found)
  
  Reading symbols from /usr/lib/libwrap.so.0...(no debugging symbols 
found)...done.
  Loaded symbols for /usr/lib/libwrap.so.0
  Reading symbols from /usr/lib/libutil.so.7...(no debugging symbols 
found)...done.
  Loaded symbols for /usr/lib/libutil.so.7
  Reading symbols from /usr/lib/libc.so.12...(no debugging symbols 
found)...done.
  Loaded symbols for /usr/lib/libc.so.12
  Reading symbols from /usr/libexec/ld.elf_so...
  (no debugging symbols found)...done.
  Loaded symbols for /usr/libexec/ld.elf_so
  Core was generated by `rpcbind.
  Program terminated with signal 11, Segmentation fault.
  #0  0x00007f7ffd7c90e7 in closelog () from /usr/lib/libc.so.12
  (gdb) bt
  #0  0x00007f7ffd7c90e7 in closelog () from /usr/lib/libc.so.12
  #1  0x00007f7ffd7c917c in openlog_r () from /usr/lib/libc.so.12
  #2  0x00000000004043f5 in main ()
  (gdb) 

Reverting to a /lib/libc.* before this change makes my machine boot up
normally again.

Does anybody else see this?

Markus.