Bind Crashing on Domain Transfer
Adam Tkac
atkac at redhat.com
Mon Feb 4 13:21:24 UTC 2008
On Wed, Jan 30, 2008 at 02:13:22PM -0800, Scott Baker wrote:
> JINMEI Tatuya / 神明達哉 wrote:
> > Does this one provide any meaningful result?
> > (gdb) thread apply all bt full
>
> Looks like not:
>
> (gdb) thread apply all bt full
>
> Thread 7 (process 6665):
> #0 0x0012d410 in __kernel_vsyscall ()
> No symbol table info available.
> #1 0x004c8c07 in ?? ()
> No symbol table info available.
> #2 0x0046c214 in ?? ()
> No symbol table info available.
> #3 0xbfa50e80 in ?? ()
> No symbol table info available.
> #4 0xbfa50f00 in ?? ()
> No symbol table info available.
> #5 0xbfa50f98 in ?? ()
> No symbol table info available.
> #6 0x0044ab72 in ?? ()
> No symbol table info available.
> #7 0xbfa50e80 in ?? ()
> No symbol table info available.
> #8 0xbfa50f04 in ?? ()
> No symbol table info available.
> #9 0x00000004 in ?? ()
> No symbol table info available.
> #10 0x00000000 in ?? ()
> No symbol table info available.
>
> Thread 6 (process 6666):
> #0 0x0012d410 in __kernel_vsyscall ()
> No symbol table info available.
> #1 0x0048f5d5 in ?? ()
> No symbol table info available.
> #2 0x00000000 in ?? ()
> No symbol table info available.
>
> ---Type <return> to continue, or q <return> to quit---
> Thread 5 (process 6668):
> #0 0x0012d410 in __kernel_vsyscall ()
> No symbol table info available.
> #1 0x0048f5d5 in ?? ()
> No symbol table info available.
> #2 0x00000000 in ?? ()
> No symbol table info available.
>
> Thread 4 (process 6669):
> #0 0x0012d410 in __kernel_vsyscall ()
> No symbol table info available.
> #1 0x0048f5d5 in ?? ()
> No symbol table info available.
> #2 0x00000000 in ?? ()
> No symbol table info available.
>
> Thread 3 (process 6670):
> #0 0x0012d410 in __kernel_vsyscall ()
> No symbol table info available.
> #1 0x0048f902 in ?? ()
> No symbol table info available.
> #2 0x00000000 in ?? ()
> No symbol table info available.
>
> Thread 2 (process 6671):
> #0 0x0012d410 in __kernel_vsyscall ()
> No symbol table info available.
> #1 0x0056b5f1 in ?? ()
> No symbol table info available.
> #2 0x0046c214 in ?? ()
> No symbol table info available.
> #3 0x00000000 in ?? ()
> No symbol table info available.
> ---Type <return> to continue, or q <return> to quit---
>
> Thread 1 (process 6667):
> #0 0x001a7996 in _start () from /lib/ld-linux.so.2
> No symbol table info available.
> #1 0xb3e469f8 in ?? ()
> No symbol table info available.
> #2 0x00000002 in ?? ()
> No symbol table info available.
> #3 0x0026d8e8 in ?? ()
> No symbol table info available.
> #4 0x002918e4 in ?? ()
> No symbol table info available.
> #5 0x002918e4 in ?? ()
> No symbol table info available.
> #6 0xb752cdd4 in ?? ()
> No symbol table info available.
> #7 0xb752ce48 in ?? ()
> No symbol table info available.
> #8 0x00189c93 in ?? ()
> No symbol table info available.
> #9 0x0000966b in ?? ()
> No symbol table info available.
> #10 0xaf724fc8 in ?? ()
> No symbol table info available.
> #11 0xb3e46918 in ?? ()
> No symbol table info available.
> #12 0x00000006 in ?? ()
> No symbol table info available.
> #13 0x00000000 in ?? ()
> No symbol table info available.
>
>
> --
> Scott Baker - Canby Telcom
> RHCE - System Administrator - 503.266.8253
>
>
I think this bind is compiled from RH source rpm. You have to install
bind-debuginfo package to get useful information (same version as your
bind rpm)
Adam
--
Adam Tkac, Red Hat, Inc.
More information about the bind-users
mailing list