After a recent update, whenever I try to run the pkgdb (or any other command that in turn calls pkgdb I get an error resulting in a core dump: [Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 24 packages found (-1 +2) (...).ruby18 in free(): error: chunk is already free Abort (core dumped) Here is the output of pkg_version -v apache-2.0.50_3 < needs updating (port has 2.0.55_4) autoconf-2.59_2 = up-to-date with port automake-1.8.5_2 < needs updating (port has 1.9.6) cvsup-without-gui-16.1h < needs updating (port has 16.1h_2) db42-4.2.52_3 < needs updating (port has 4.2.52_4) exim-4.42+27 < needs updating (port has 4.60) expat-1.95.8 < needs updating (port has 2.0.0_1) ezm3-1.2 = up-to-date with port gettext-0.13.1_1 < needs updating (port has 0.14.5_2) gmake-3.80_2 = up-to-date with port help2man-1.33.1 < needs updating (port has 1.36.3) libiconv-1.9.2_1 < needs updating (port has 1.9.2_2) libtool-1.5.8 < needs updating (port has 1.5.22_2) m4-1.4.1 < needs updating (port has 1.4.4) mod_fcgid-0.80 < needs updating (port has 1.07) neon-0.24.7 < needs updating (port has 0.25.4_1) openssl-0.9.8a = up-to-date with port p5-gettext-1.01_4 < needs updating (port has 1.05_1) perl-5.8.8 = up-to-date with port portupgrade-20040701_3 < needs updating (port has 2.0.1_1,1) ruby-1.8.4_4,1 = up-to-date with port ruby18-bdb1-0.2.2 = up-to-date with port ruby18-gems-0.8.11 = up-to-date with port subversion-1.0.8 < needs updating (port has 1.3.0_4) Should I also include the core dump? Thanks in advance.
On Thursday 23 March 2006 11:11, Kaveh Ahmadian wrote:> After a recent update, whenever I try to run the pkgdb (or any other > command that in turn calls pkgdb I get an error resulting in a core dump: > > [Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 24 packages > found (-1 +2) (...).ruby18 in free(): error: chunk is already free > Abort (core dumped)I've seen this a number of times; it usually means a corrupt pkgdb. Rebuild it from scratch (pkgdb -fu). If that fails or if you still get the error afterwards, rebuild and reinstall portupgrade and ruby (without using portupgrade in the process). Run 'pkgdb -fu' again after the reinstall. JN
On Thursday 23 March 2006 11:53, John Nielsen wrote:>I've seen this a number of times; it usually means a corrupt pkgdb. Rebuild>it from scratch (pkgdb -fu). If that fails or if you still get the error >afterwards, rebuild and reinstall portupgrade and ruby (without using >portupgrade in the process). Run 'pkgdb -fu' again after the reinstall. > >JNThanks. I did a 'make deinstall' in the /usr/ports/sysutils/portupgrade directory, then ran 'make install clean'. After I did a 'pkgdb -fu', I was all set.