Re: HEADSUP: Something has gone south with -current

On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote:
> On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote:
> > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote:
> > > 
> > > make core dumps.
> > > devd core dumps.
> > > init core dumps.
> > > cc   core dumps.  
> > > c++  core dumps.
> > > 
> > > Something seems to be broken.
> > > 
> > 
> > Further investigation,
> > as core dumps.
> > cpp core dumps.
> > /rescue/vi core dumps.
> > 
> > All of these programs are statically linked.  Note, ar and ranlib
> > have static linkage, and appear to still work but these were not
> > replaced by the failing 'make installworld'.
> > 
> > Ah, so if I go into /usr/obj/usr/src/amd64.amd64/ar, this ar
> > is static and not stripped and works!  But, if I do
> > 
> > cp ar ar.new
> > strip ar
> > ./ar
> > 
> > This ar core dumps.  So, stripping static binaries seems to 
> > break the binary.
> > 
> 
> Yep, definitely, a problem with stripping static binaries.
> 
> I copied both init and devd from /usr/obj to /sbin without
> stripping the binaries.  System rebooted as expected.
> 

Don't know if it's valid, but

% ./ar
% gdb82 ar.new ar.core
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000000029386c in __je_malloc_tsd_boot0 ()
(gdb) bt
#0  0x000000000029386c in __je_malloc_tsd_boot0 ()
#1  0x00000000002b6d08 in calloc ()
#2  0x000000000028275b in _thr_alloc ()
#3  0x000000000027ec98 in _libpthread_init ()
#4  0x000000000024d239 in handle_static_init ()
#5  0x000000000024d10e in _start ()


-- 
Steve