At 09:39 AM 10/13/2002, you wrote:
> > segfault case. What is surprising is that you have a machine with three
> > other AOLserver instances and not all of them exhibit the problem. That's
> > just goofy.
>
>The resolver library could be dynamically linked in some of the server
>builds and statically linked in others. I dunno - just a guess. On
>Linux you can check to see which dynamic libraries an executable is
>using by using ldd <executable>, for example:
>
>$ ldd nsd
> libdl.so.2 => /lib/libdl.so.2 (0x2aac1000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x2aac5000)
> libm.so.6 => /lib/libm.so.6 (0x2aad6000)
> libc.so.6 => /lib/libc.so.6 (0x2aaf2000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaab000)
I am using the same binary file on disk to launch all three instances of
aolserver on that machine.
This is what ldd comes up with on my end on the wierd one of the two.
libdl.so.2 => /lib/libdl.so.2 (0x4001e000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40022000)
libm.so.6 => /lib/libm.so.6 (0x40039000)
libc.so.6 => /lib/libc.so.6 (0x4005c000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Patrick Spence <ariven AT ariven DOT com>
www.RandomRamblings.com
www.Ariven.com
