Re: segmentation fault(s) after upgrading to CURRENT

Dominic Marks wrote:
> On Thu, 5 Oct 2006 12:52:17 +0100 (BST)
> rainbowit_at_Rainbow-IT.net wrote:
> 
>> Hi All,
>>
>> I'm new to the list, so please be gentle :)
> 
> Hi Chris,
> 
>> I have just upgraded from FreeBSD_6 STABLE to FreeBSD_7 CURRENT (about
>> time I did some testing / early adoption I thought).
>>
>> [12:49]chrisp_at_valhalla ~ % uname -a
>> FreeBSD valhalla.systems.hq.inty.net 7.0-CURRENT FreeBSD 7.0-CURRENT #1:
>> Thu Oct  5 09:38:09 BST 2006    
>> chrisp_at_valhalla.systems.hq.inty.net:/usr/obj/usr/src/sys/VALHALLA  i386
>>
>> My 'VALHALLA' kernel is a copy of 'GENERIC', but with
>> RAID/SCSI/FIREWIRE/ISA_NICs removed.
>>
>> I have completed the upgrade but now I see many of the programs I run, are
>> core dumping...
> 
> Rebuild them. From what I can see they mostly look to be
> threaded apps. You might find that doing a fresh install of
> CURRENT is a better idea in future. Although I suppose then you
> wouldn't be testing the upgrade path.
> 
>> This is from /var/log/messages: -
>>
>> Oct  5 11:26:26 valhalla kernel: pid 805 (gdm-binary), uid 0: exited on
>> signal 11 (core dumped)
>> Oct  5 11:26:29 valhalla kernel: pid 897 (my_print_defaults), uid 88:
>> exited on signal 11
>> Oct  5 11:26:29 valhalla kernel: pid 898 (my_print_defaults), uid 88:
>> exited on signal 11
>> Oct  5 11:26:29 valhalla kernel: pid 914 (mysqld), uid 88: exited on
>> signal 11
>> Oct  5 11:26:35 valhalla kernel: pid 942 (clamd), uid 0: exited on signal
>> 11 (core dumped)
>> Oct  5 11:26:35 valhalla kernel: pid 946 (freshclam), uid 0: exited on
>> signal 11 (core dumped)
>> Oct  5 11:26:35 valhalla root: /etc/rc: WARNING: $compat5x_enable is not
>> set properly - see rc.conf(5).
>> Oct  5 11:26:36 valhalla kernel: pid 1025 (gdomap), uid 0: exited on
>> signal 11 (core dumped)
>> Oct  5 11:26:36 valhalla kernel: pid 1039 (gdnc), uid 0: exited on signal
>> 11 (core dumped)
>>
>> I've read the mailarchive and added 'compat5x_enable="YES"' to
>> /etc/rc.conf (I think that's what I should have done and the warning has
>> gone away now).
>>
>> As for the Segmentation faults, what should I do to get myself back on track?
>>
>> I an eager to do whatever it takes, to help diagnose and fix what's wrong.
>>
>> Kindest Regards,
>> --
>>
>> ChrisP
>>
>> _______________________________________________
>> freebsd-current_at_freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"

Hi Dom,

Yeah, the system was pretty-much OK, just a few programs that needed to 
be rebuilt.

For the record/archives, I started by rebuilding 'ruby18' by doing: -

/usr/ports/lang/ruby18 #  make clean distclean deinstall reinstall

which worked a treat and then similar in /usr/ports/sysutils/portupgrade 
(as poerupgrade was one of the programs that were seg-faulting).

Then I just rebuilt the programs most important to me 
(firefox/thunderbird/enigmail etc), using 'portupgrae -rR <program>' and 
I'm almost back to normal now.

Thanks for the speedy responses everybody!

Cheers :)
-- 

Chris Phillips