Subject: Re: recent libc (bind?) changes breaks my asterisk on cobalt qube
To: None <>
From: Christos Zoulas <>
List: port-cobalt
Date: 02/09/2007 19:05:08
In article <>,
Markus W Kilbinger  <> wrote:
>Recent libc changes between Jan 26th and Feb 2nd break my
>(pkgsrc/comms/) asterisk running on my cobalt qube (running actual
>  cochise# gdb /usr/pkg/sbin/asterisk /asterisk.core-new-libc          
>  GNU gdb 5.3nb1
>  Copyright 2002 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 "mipsel--netbsd"...(no debugging symbols found)...
>  Core was generated by `asterisk'.
>  Program terminated with signal 11, Segmentation fault.
>  Reading symbols from /usr/lib/ debugging symbols
>  done.
>  [...]
>  Reading symbols from /usr/libexec/ld.elf_so...done.
>  Loaded symbols for /usr/libexec/ld.elf_so
>  #0  0x7db93af8 in __res_nclose () from /usr/lib/
>  (gdb) bt
>  #0  0x7db93af8 in __res_nclose () from /usr/lib/
>  #1  0x7db93c70 in __res_ndestroy () from /usr/lib/
>  #2  0x7db947c8 in __res_vinit () from /usr/lib/
>  #3  0x0047cc38 in ast_search_dns ()
>  warning: Warning: GDB can't find the start of the function at 0xffffffff.
>This seems to be related to the bind changes within libc. libc
>compiled from Jan 26th sources runs fine with my (unchanged) asterisk
>Has anybody an idea what's going wrong here?

Do you have res_init.c 1.11?