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?

Tom

-- fedora-devel-java-list mailing list fedora-devel-java-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-java-list

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 [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 (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151116096 (LWP 22135)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -151116096 (LWP 22135)] 0x07420917 in _Jv_RegisterClassHookDefault () from /usr/lib/libgcj_fc4.so.6 (gdb) bt #0 0x07420917 in _Jv_RegisterClassHookDefault () from /usr/lib/libgcj_fc4.so.6 #1 0x0742078a in _Jv_RegisterClasses () from /usr/lib/libgcj_fc4.so.6 #2 0x08049c2a in ?? () #3 0x0804c010 in ?? () #4 0xfee5cf94 in ?? () #5 0x073fb31d in _Jv_Malloc () from /usr/lib/libgcj_fc4.so.6 #6 0x08049864 in _init () #7 0x0804ae4a in ?? () #8 0x07862004 in ?? () from /usr/lib/libgcj_fc4.so.6 #9 0x0069dff4 in ?? () from /lib/tls/libc.so.6 #10 0x00000000 in ?? () (gdb)

Tom

-- fedora-devel-java-list mailing list fedora-devel-java-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-java-list

On Tue, 2005-02-22 at 19:07 -0500, Thomas Fitzsimmons wrote:

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

[snip]

In the end I got things working; I did a "yum update gcc4-java", then a "yum remove eclipse-platform" for good measure.

I then did a "yum install eclipse-gtk2 eclipse-jdt" and got this: [snip] Running Transaction Installing: eclipse-gtk2 100 % done 1/3 Installing: eclipse-jdt 100 % done 2/3 error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db error: %post(eclipse-jdt-3.0.1_fc-14.i386) scriptlet failed, exit status 2 Installing: eclipse-platform 100 % done 3/3 error: could not update /usr/lib/eclipse/eclipse.db: java.lang.IllegalArgumentException: eclipse.db (hundreds of similar lines follow)

error: %post(eclipse-platform-3.0.1_fc-14.i386) scriptlet failed, exit status 2

Installed: eclipse-gtk2.i386 1:3.0.1_fc-14 eclipse-jdt.i386 1:3.0.1_fc-14 Dependency Installed: eclipse-platform.i386 1:3.0.1_fc-14 Complete!

However, Eclipse started up OK (albeit with an error): [dmalcolm@cassandra fedora-updates]$ eclipse Warning: -Xms64M not understood. Ignoring. Warning: -Xmx256M not understood. Ignoring.

and it seems to be working - tempting the fates here :-) Awesome!

BTW I didn't seem to get a splash screen.

Hope the above information is of use.

Dave