On Thu, Jan 08, 2015 at 02:06:16PM +0000, Bjoern A. Zeeb wrote: > > > On 08 Jan 2015, at 13:37 , [email protected] wrote: > > > > On Thu, Jan 08, 2015 at 01:40:11PM +0100, Dimitry Andric wrote: > >> On 08 Jan 2015, at 13:09, Bjoern A. Zeeb <[email protected]> > >> wrote: > >>> > >>>> On 07 Jan 2015, at 15:02 , Bjoern A. Zeeb > >>>> <[email protected]> wrote: > >>>>> On 07 Jan 2015, at 14:13 , Ed Maste <[email protected]> wrote: > >>>>> On 7 January 2015 at 08:57, David Wolfskill <[email protected]> > >>>>> wrote: > >>>>>> --- kernel.debug --- > >>>>>> linking kernel.debug > >>>>>> ctfmerge -L VERSION -g -o kernel.debug ... > >>>>>> Segmentation fault (core dumped) > >>>>>> *** [kernel.debug] Error code 139 > >>>>> ... > >>>>>> I'm mostly wondering what "Error code 139" is intended to mean.... :-} > >>>>> > >>>>> It's the way termination due to a signal is reported. The exit status > >>>>> is 128 + the signal number and SIGSEGV = 11. > >>>> > >>>> I did see it twice last night while doing HEAD builds, and i386.GENERIC > >>>> only. For later builds it was just gone again. Not sure if anyone > >>>> wants to figure out what was special about the two SVN revisions. For > >>>> me it was a cross-build from amd64 as part of make universe. > >>> > >>> Ok, this continues; I have since seen it four more times. Still > >>> i386.GENERIC only; none of the LINT kernels or other architectures. > >>> > >>> Can someone please investigate what triggers this? > >> > >> Looks like a stack overflow, cause unknown as of yet: > > > > I'll try to reproduce this, but perhaps try reverting r274569? r274565 > > and r274564 could also potentially be the cause of this, but r274569 > > would be my first guess. > > It only started 2 nights ago and we are both doing daily builds. Unlikely > that stuff from November would do it oh so suddenly. > > It’s hard to exactly narrow it down as there was a lot of other breakage in > the tree but I know that r276729 finished a full universe and I hadn’t > noticed the problem before. So I would almost assume it was something after > that (but obviously it could be a combination of things).
Ok, I was able to reproduce the crash by cross-compiling i386 on amd64. Reverting r274569 made it go away for me. I'm going to try a few more times to see if it's consistent. -Mark _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[email protected]"
