SIGSEGV in /bin/sh after r322740 -> r322776 update

[David Wolfskill]

On Tue, Aug 22, 2017 at 06:34:42PM +0300, Konstantin Belousov wrote:
> ...
> > Bisection time?  Or if there's another approach (or even a suggestion
> > for a revision to try first), I'm up for it.  9And yes, I'll just
> > be rebuilding the kernel for the rest of this exercise, I think.
> > That should speed things up significantly.)
> 
> No need.  It is clearly something with r322762 (more likely) or
> r322763 (less likely).

Ah.

> Give me some time, I either fix it today or revert the commits.

Cool.  I'm at work now, but if there's anything I can do (e.g.,
testing), I will do what I can: I have serial console access to the
machine (for example).

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
If we wish to eliminate sources of Fake News, start at the top: D. Trump.

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/20170822/fc8418e8/attachment.sig>