[bind10-dev] failed lettuce master 812392465ae1ffa4a583186fd48f4c7aff1640dd

Shane Kerr shane at isc.org
Wed Oct 24 10:29:20 UTC 2012


JINMEI,

On Tuesday, 2012-10-23 16:23:29 -0700, 
JINMEI Tatuya / 神明達哉 <jinmei at isc.org> wrote:
> At Mon, 22 Oct 2012 12:52:39 -0500 (CDT),
> "Jeremy C. Reed" <jreed at isc.org> wrote:
> > 
> > On Mon, 22 Oct 2012, tester at isc.org wrote:
> > 
> > > http://git.bind10.isc.org/~tester/builder//BIND10-lettuce/20121022170501-MacOS/logs/lettuce.out
> > > 
> > > http://git.bind10.isc.org/~tester/builder//builder.html
> > > 
> > > master 812392465ae1ffa4a583186fd48f4c7aff1640dd 1350917219
> > > 
> > > Last successful master revision (for lettuce):
> > > ae2e285fb9abc9295563206d86ebbf94dc4f8918
> > > 
> > > Macmini, x86_64, CLang
> > 
> > 
> > The logs at 
> > http://git.bind10.isc.org/~tester/builder//BIND10-lettuce/20121022170501-MacOS/logs/files/tests/lettuce/output/Xfrin-Retransfer_command-bind10.stderr
> > show:
> > 
> > 2012-10-22 10:26:27.674 INFO  [b10-boss.boss] BIND10_PROCESS_ENDED 
> > process 79181 of b10-auth ended with status 138 2012-10-22
> > 10:26:27.674 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
> > component b10-auth (pid 79181) failed: process dumped core with
> > exit status 138 (killed by signal 10: SIGBUS)
> > 
> > Here is the backtrace of /cores/core.79181
> 
> I couldn't reproduce this for the latest master
> (3404981c39241b4463e661981614ec0d157b924d) on the macmini box.

That's scary. Is there anything that can cause SIGBUS on OS X other than
a coding error? (Like... broken fan making the box overheat, or bad
memory, or...)

--
Shane


More information about the bind10-dev mailing list