Re: Crashes in libthr?

This may have been my screw up....


On March 15, 2016 12:05:03 PM Bryan Drewery <bdrewery_at_FreeBSD.org> wrote:

> On 3/14/16 8:03 PM, Larry Rosenman wrote:
>> On 2016-03-14 21:49, Larry Rosenman wrote:
>>> On 2016-03-14 18:49, Larry Rosenman wrote:
>>>> On 2016-03-14 18:47, Steven Hartland wrote:
>>>>> On 14/03/2016 22:28, Larry Rosenman wrote:
>>>>>> On 2016-03-14 17:25, Poul-Henning Kamp wrote:
>>>>>>> --------
>>>>>>> In message <20160314222228.GA1753_at_borg.lerctr.org>, Larry Rosenman
>>>>>>> writes:
>>>>>>>
>>>>>>>> And sshd is busted.
>>>>>>>
>>>>>>> FYI: I seeing no such issues on two systems running:
>>>>>>>
>>>>>>>     11.0-CURRENT #4 r296808: Sun Mar 13 22:39:59 UTC 2016
>>>>>>> and
>>>>>>>     11.0-CURRENT #32 r296137: Sat Feb 27 11:34:01 UTC 2016
>>>>>> As I said it's this ONE box, even doing an install from the other
>>>>>> (RUNNING) boxes
>>>>>> /usr/src,/usr/obj).
>>>>>>
>>>>>> This build was at:
>>>>>> borg.lerctr.org /usr/src $ svn info
>>>>>> Path: .
>>>>>> Working Copy Root Path: /usr/src
>>>>>> URL: https://svn.freebsd.org/base/head
>>>>>> Relative URL: ^/head
>>>>>> Repository Root: https://svn.freebsd.org/base
>>>>>> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
>>>>>> Revision: 296823
>>>>>> Node Kind: directory
>>>>>> Schedule: normal
>>>>>> Last Changed Author: adrian
>>>>>> Last Changed Rev: 296823
>>>>>> Last Changed Date: 2016-03-13 23:39:35 -0500 (Sun, 13 Mar 2016)
>>>>>>
>>>>>> borg.lerctr.org /usr/src $
>>>>>>
>>>>>>
>>>>>> I can post the make.conf.
>>>>>>
>>>>>> It's really weird.
>>>>> Silly question your not building on an NFS FS are you?
>>>>>
>
>>>> No, this is local disk.  The "install from other machine" was via
>>>> NFS......
>>>
>>>
>>> I found it.  A bad version (from march 8th or so) of
>>> /lib/libprivatessh.so.5 that did NOT export the symbol, but the
>>> version in /usr/lib/libprivatessh.so.5 DID export the symbol.
>>>
>>> I wiped out the /lib/libprivate* and re-did installworld.
>>>
>>> and all seems fine now.
>>>
>>> I suspect I hit a time when the tree had bad stuff installing into
>>> /lib/libprivate*
>>
>>
>> BTW, there were LOTS of OTHER things in /lib with the same bad date,
>> which I've now cleaned up.
>>
>> make delete-old{-libs} did *NOT* clean this up.
>>
>>
>
> These were dated March 8 2016?  I don't recall any recent changes
> causing libraries to be installed to the wrong place.
>
> --
> Regards,
> Bryan Drewery