ino64? r318606 -> r318739 OK; r318739 -> r318781 fails SIGSEGV
David Wolfskill
david at catwhisker.org
Wed May 24 13:59:07 UTC 2017
On Wed, May 24, 2017 at 04:35:58PM +0300, Konstantin Belousov wrote:
> ...
> > (lldb) bt
> > * thread #1, name = 'ld', stop reason = signal SIGSEGV
> > * frame #0: 0x0000000000000000
> > (lldb)
> >
> > which isn't entirely unexpected, I suppose, given the nature of SIGSEGV.
> Useful gdb is in ports, devel/gdb.
OK; thanks.
> There is nothing in the nature of SIGSEGV which makes lack of the
> backtrace a reasonable outcome.
Oh; OK.
> ...
> If build of r318739 succed, can you try, please, to rebuild the current
> latest sources, but now with reverted r318750 ?
It did complete successfully.
I have updated /usr/src back to 318781, then started a new build.
While it has not yet completed ">>> stage 4.2: building libraries", it
is well beyond the provious point of failure (again, building parts of
clang/libllvm).
I'm reporting now, as I'll need to head in to work fairly soon. I
should be able to report definitively a bit later.
Thank you for your help!
Peace,
david
--
David H. Wolfskill david at catwhisker.org
"[T]he president’s improper efforts to influence an ongoing investigation"
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20170524/e7c801ad/attachment.sig>
More information about the freebsd-current
mailing list