[Bug 458198] Re: host crashed with SIGSEGV in start_thread()
pmitra at gmail.com
Sat Nov 28 03:59:23 GMT 2009
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
<chuck.short at canonical.com>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()
> 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
> 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
> ?? () 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
host crashed with SIGSEGV in start_thread()
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
More information about the Ubuntu-server-bugs