portupgrade core dumps

2006-07-08 Thread Neil Short
Suddenly, portupgrade (and it's associated tools)
instantly core dumps.

any insight? Is my ports database boned?

here is some sample output:

bright# portupgrade portupgrade
Segmentation fault (core dumped)
bright# dmesg | tail
pid 15403 (ruby18), uid 0: exited on signal 11 (core
dumped)
pid 15579 (ruby18), uid 0: exited on signal 11 (core
dumped)
pid 15770 (ruby18), uid 0: exited on signal 11 (core
dumped)
pid 15826 (ruby18), uid 0: exited on signal 11 (core
dumped)
pid 16045 (ruby18), uid 0: exited on signal 11 (core
dumped)
pid 16658 (gst-register-0.8), uid 0: exited on signal
11 (core dumped)
pid 16711 (gtk-update-icon-cac), uid 0: exited on
signal 11 (core dumped)
pid 17069 (ruby18), uid 0: exited on signal 11 (core
dumped)
pid 17070 (ruby18), uid 0: exited on signal 11 (core
dumped)
pid 17081 (ruby18), uid 0: exited on signal 11 (core
dumped)
bright# cd /usr/ports/sysutils/portupgrade
bright# make clean
===  Cleaning for ruby-1.8.4_8,1
===  Cleaning for ruby18-bdb-0.5.9
===  Cleaning for perl-5.8.8
===  Cleaning for db41-4.1.25_3
===  Cleaning for portupgrade-2.1.3.2,2
bright# make
===  Vulnerability check disabled, database not found
===  Extracting for portupgrade-2.1.3.2,2
= MD5 Checksum OK for pkgtools-2.1.3.2.tar.bz2.
= SHA256 Checksum OK for pkgtools-2.1.3.2.tar.bz2.
===   portupgrade-2.1.3.2,2 depends on file:
/usr/local/bin/ruby18 - found
===  Patching for portupgrade-2.1.3.2,2
===   portupgrade-2.1.3.2,2 depends on file:
/usr/local/bin/ruby18 - found
===   portupgrade-2.1.3.2,2 depends on file:
/usr/local/bin/ruby18 - found
===  Configuring for portupgrade-2.1.3.2,2
===  Building for portupgrade-2.1.3.2,2
=== bin (all)
Warning: Object directory not changed from original
/usr/ports/sysutils/portupgrade/work/pkgtools-2.1.3.2/bin
/usr/local/bin/ruby18 -wc pkg_fetch
*** Signal 11

Stop in
/usr/ports/sysutils/portupgrade/work/pkgtools-2.1.3.2/bin.
*** Error code 1

Stop in
/usr/ports/sysutils/portupgrade/work/pkgtools-2.1.3.2.
*** Error code 1

Stop in /usr/ports/sysutils/portupgrade.
bright# uname -a
FreeBSD bright.sunset 7.0-CURRENT FreeBSD 7.0-CURRENT
#2: Fri Jul  7 21:35:41 MST 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/BRIGHT  i386


==
Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all 
his works are truth, and his ways are justice; and he is able to bring low 
those who walk in pride.
Daniel 4:37

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: portupgrade core dumps

2006-07-08 Thread Neil Short


--- Neil Short [EMAIL PROTECTED] wrote:

 Suddenly, portupgrade (and it's associated tools)
 instantly core dumps.
 

followup:
force reinstall/reregister of /usr/ports/lang/ruby18
did the trick.

==
Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all 
his works are truth, and his ways are justice; and he is able to bring low 
those who walk in pride.
Daniel 4:37

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]