1.5 badly broken, can it be fixed?

Question

I'm working under the following system:
07:08:00$ uname -a
Linux dragon 2.6.4-gentoo #13 SMP Fri Mar 26 01:42:12 EST 2004 x86_64 5 GNU/Linux
[linguist@dragon] sl=1 /usr/src/linux
07:13:18$ grep . /proc/cpuinfo /dev/null
/proc/cpuinfo:processor : 0
/proc/cpuinfo:vendor_id : AuthenticAMD
/proc/cpuinfo:cpu family : 15
/proc/cpuinfo:model : 5
/proc/cpuinfo:model name : AMD Opteron(tm) Processor 244
/proc/cpuinfo:stepping : 8
/proc/cpuinfo:cpu MHz : 1789.423
/proc/cpuinfo:cache size : 1024 KB
/proc/cpuinfo:fpu : yes
/proc/cpuinfo:fpu_exception : yes
/proc/cpuinfo:cpuid level : 1
/proc/cpuinfo:wp : yes
/proc/cpuinfo:flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow
/proc/cpuinfo:bogomips : 3522.56
/proc/cpuinfo:TLB size : 1088 4K pages
/proc/cpuinfo:clflush size : 64
/proc/cpuinfo:address sizes : 40 bits physical, 48 bits virtual
/proc/cpuinfo:power management: ts ttp
/proc/cpuinfo:processor : 1
/proc/cpuinfo:vendor_id : AuthenticAMD
/proc/cpuinfo:cpu family : 15
/proc/cpuinfo:model : 5
/proc/cpuinfo:model name : AMD Opteron(tm) Processor 244
/proc/cpuinfo:stepping : 8
/proc/cpuinfo:cpu MHz : 1789.423
/proc/cpuinfo:cache size : 1024 KB
/proc/cpuinfo:fpu : yes
/proc/cpuinfo:fpu_exception : yes
/proc/cpuinfo:cpuid level : 1
/proc/cpuinfo:wp : yes
/proc/cpuinfo:flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow
/proc/cpuinfo:bogomips : 3571.71
/proc/cpuinfo:TLB size : 1088 4K pages
/proc/cpuinfo:clflush size : 64
/proc/cpuinfo:address sizes : 40 bits physical, 48 bits virtual
/proc/cpuinfo:power management: ts ttp
And a formidable beast it is. But I'm finding that both 1.5.beta1 and 1.4.2 are segfaulting with alarming regularity.
As a matter of face, they're basicly useless. So the real truth is that I'm working on a $5000 Xserver, using it as
a dumb client, and sshing to my old athlon box to actually use the jdk/eclipse.
But I thought ... what the hell? I'm a programmer. I fix things. I'll fix it.
I cannot seem to find the 1.5 source to save my life. Or to save my productivity. This seems absurd, since the
time you really want people fixing your code is when it's in beta. What gives? Have the gods gone crazy?

Answer 1

There's probably nothing wrong with the $5000 X-server
since all it does is display the output of a program
running on your other computer. I've never had Java
1.4.2 actually segfault though, just freeze sometimes.
Maybe there's a problem with something else on your
Athlon box, or with Eclipse (especially if it's not a
stable release).The sad thing is that the other computer, though it ran
fine in it's day, has nowhere near the power of the new
amd64 box ... but I can't get the jdk stable enough to
develop with on the amd64.