host crashed with SIGSEGV in start_thread()

[PM]

Binary package hint: bind9

This happened while configuring the network interface eth0

ProblemType: Crash
Architecture: i386
Date: Thu Oct 22 19:32:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/host
Package: bind9-host 1:9.6.1.dfsg.P1-3
ProcCmdline: host -t soa local.
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x835fa3: mov %edx,0x18(%eax)
 PC (0x00835fa3) ok
 source "%edx" ok
 destination "0x18(%eax)" (0x00000017) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: bind9
StacktraceTop:
 ?? () from /usr/bin/host
 ?? () from /usr/lib/libisc.so.50
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: host crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

[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!

[PM (pmitra)]

I'm sorry, my installation crashed totally a day or so later. I guess this
may have been the first signal of that happening.
Apparently there was a hardware issue. Though not sure, i believe this issue
can safely be closed.

I appreciate the really great response i received from you.

On Thu, Nov 26, 2009 at 12:49 AM, Chuck Short <email address hidden>wrote:

> 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!
>
> --
> host crashed with SIGSEGV in start_thread()
> https://bugs.launchpad.net/bugs/458198
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “bind9” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: bind9
>
> This happened while configuring the network interface eth0
>
> ProblemType: Crash
> Architecture: i386
> Date: Thu Oct 22 19:32:03 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/host
> Package: bind9-host 1:9.6.1.dfsg.P1-3
> ProcCmdline: host -t soa local.
> ProcEnviron: PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
> SegvAnalysis:
> Segfault happened at: 0x835fa3: mov %edx,0x18(%eax)
> PC (0x00835fa3) ok
> source "%edx" ok
> destination "0x18(%eax)" (0x00000017) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: bind9
> StacktraceTop:
> ?? () from /usr/bin/host
> ?? () from /usr/lib/libisc.so.50
> start_thread () from /lib/tls/i686/cmov/libpthread.so.0
> clone () from /lib/tls/i686/cmov/libc.so.6
> Title: host crashed with SIGSEGV in start_thread()
> Uname: Linux 2.6.31-14-generic i686
> UserGroups:
>

[Chuck Short (zulcss)]

Thanks for the response closing then.

Regards
chuck

[efa (efa)]

in my case, is not an hardware problem