On Tue, 2005-02-22 at 17:24 -0500, David Malcolm wrote: > On Mon, 2005-02-21 at 22:22 -0500, Thomas Fitzsimmons wrote: > >On Mon, 2005-02-21 at 18:26 -0500, David Malcolm wrote: > >>On Mon, 2005-02-21 at 16:20 -0500, Thomas Fitzsimmons wrote: > >>>On Mon, 2005-02-21 at 15:36 -0500, David Malcolm wrote: > >>>>I get the following error when trying to update Eclipse packages from > >>>>Rawhide: > >>>> > >>>>yum update eclipse-ecj eclipse-platfrom eclipse-gtk2 eclipse-jdt > >>>> > >>>>Error: java-1.4.2-gcj4-compat-devel conflicts: > >>>>java-1.4.2-gcj-compat-devel<= 1.4.2.0-39jpp > >>>>Error: java-1.4.2-gcj4-compat conflicts: java-1.4.2-gcj-compat<= > >>>>1.4.2.0-39jpp > >>>> > >>> > >>>java-1.4.2-gcj4-compat-devel should obsolete > >>>java-1.4.2-gcj-compat-devel. I guess I'll remove the Conflicts lines > >>>from the next release. > >>> > >>>>So which gcj-compat do I want? > >>>> > >>>java-1.4.2-gcj4-compat and java-1.4.2-gcj4-compat-devel. > >> > >>OK, when I installed the new packages I got lots of errors like this: > >>Updating: eclipse-ecj 100 % done 1/10 > >>/var/tmp/rpm-tmp.82380: line 3: 21207 Segmentation fault > >>gcj-dbtool4 > >>-a /usr/lib/eclipse/eclipse.db /usr/share/eclipse/plugins/org.eclipse.jdt.core_3.0.1/jdtcore.jar /usr/lib/eclipse/jdtcore.jar.so > >>/var/tmp/rpm-tmp.82380: line 6: 21264 Segmentation fault > >>gcj-dbtool4 > >>-a /usr/lib/eclipse/eclipse.db /usr/share/eclipse/plugins/org.eclipse.jdt.core_3.0.1/jdtCompilerAdapter.jar /usr/lib/eclipse/jdtCompilerAdapter.jar.so > >>error: %post(eclipse-ecj-3.0.1_fc-14.i386) scriptlet failed, exit status > >>139 > >>Installing: gjdoc 100 % done 2/10 > >>Installing: java-1.4.2-gcj4-compat 100 % done 3/10 > >>Installing: java-1.4.2-gcj4-compat-devel 100 % done 4/10 > >>Updating: libswt3-gtk2 100 % done 5/10 > >>/var/tmp/rpm-tmp.17340: line 1: 22154 Segmentation fault > >>gcj-dbtool4 -a /usr/lib/eclipse/eclipse.db $j /usr/lib/eclipse/`basename > >>$j`.so > >> > >>etc... > >> > >>and the resulting eclipse doesn't run: > >>[dmalcolm@cassandra ~]$ eclipse > >>/usr/bin/eclipse: line 45: 28121 Segmentation fault > >>LD_PRELOAD=/usr/lib/eclipse/xml-commons-apis-1.0.jar.so:/usr/lib/eclipse/xalan-j2-2.6.0.jar.so:/usr/lib/eclipse/xerces-j2-2.6.2.jar.so /usr/share/eclipse/eclipse $ECLIPSE_OPTS $@ $VM_OPTS > >> > >>Doing anything with that LD_PRELOAD line fails, e.g.: > >>[dmalcolm@cassandra~]$ > >>LD_PRELOAD=/usr/lib/eclipse/xml-commons-apis-1.0.jar.so:/usr/lib/eclipse/xalan-j2-2.6.0.jar.so:/usr/lib/eclipse/xerces-j2-2.6.2.jar.so ls > >>Segmentation fault > >> > >>Any thoughts? > >> > > > >It looks like gcj-dbtool4 is segfaulting. Can you run it with no > >arguments? What architecture are you on? You could try rebuilding > >eclipse.db by hand if gcj-dbtool4 does work on the command line. > > How do I do this by hand? > > [dmalcolm@cassandra ~]$ rpm -qf /usr/bin/gcj-dbtool4 > gcc4-java-4.0.0-0.22 > > [dmalcolm@cassandra ~]$ gcj-dbtool4 > Segmentation fault This is a problem: Andrew, shall we file a bug for this or is there one filed already? > [dmalcolm@cassandra ~]$ gdb gcj-dbtool4 > GNU gdb Red Hat Linux (6.1post-1.20040607.41rh) > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-redhat-linux-gnu"...(no debugging > symbols found)...Using host libthread_db library > "/lib/tls/libthread_db.so.1". > > (gdb) run > Starting program: /usr/bin/gcj-dbtool4 > /usr/src/build/473254-i386/BUILD/gdb > +dejagnu-20040607/gdb/dwarf2read.c:5000: internal-error: could not find > partial DIE in cache > > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) n > > /usr/src/build/473254-i386/BUILD/gdb > +dejagnu-20040607/gdb/dwarf2read.c:5000: internal-error: could not find > partial DIE in cache > > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Create a core file of GDB? (y or n) n See this bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19769 We need to get the patch there into our gcc4 rpms. Tom
