host crashed with SIGSEGV

[messajunior]

Binary package hint: bind9

I don't know.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: bind9-host 1:9.7.1.dfsg.P2-2
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Wed Sep 8 12:44:55 2010
ExecutablePath: /usr/bin/host
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100831.2)
ProcCmdline: host -t soa local.
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xf0cacc: movzbl (%eax),%eax
 PC (0x00f0cacc) ok
 source "(%eax)" (0x002f760b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: bind9
StacktraceTop:
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
Title: host crashed with SIGSEGV
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 _dl_lookup_symbol_x (
 _dl_relocate_object (scope=0xb77ed458, reloc_mode=1,
 dl_main (phdr=0xb7b034, phnum=8, user_entry=0xbfcbc9c0,
 _dl_sysdep_start (start_argptr=0xbfcbca20,
 _dl_start (arg=<value optimized out>) at rtld.c:334

[Chuck Short (zulcss)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Chuck Short (zulcss)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Chuck Short (zulcss)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!