Segmentation violation (even with ulimit -s 2048)
I had been running Blackdown 1.3.1-FCS (green threads, nojit) without any problems for over a year on a system with Linux Kernel version 2.2.16 and Glibc 2.2.4 on a Red Hat Linux 7.0 base. I've been using the "ulimit -s 2048" setting to avoid the problem that caused segmentation violations earlier in 2001 (Sun Bug Id 4466587). Now I've upgraded to all the very latest Red Hat Linux 7.0 updates: Blackdown 1.3.1-02b-FCS (green theads, nojit) kernel-2.2.22-7.0.2 glibc-2.2.4-18.7.0.7 The version strings for Blackdown and the kernel are: Classic VM (build Blackdown-1.3.1-02b-FCS, green threads, nojit) Linux www.volano.com 2.2.22-7.0.2 #1 Mon Sep 23 06:55:40 EDT 2002 i686 As before, I'm still setting: ulimit -s 2048 ulimit -n 1024 and I still start up Blackdown with the options "-green -Xmx256m -Xss64k". But now I'm getting daily segmentation violations on our server -- one or two per day: SIGSEGV 11* segmentation violation si_signo [11]: SIGSEGV 11* segmentation violation si_errno [0]: Success si_code [0]: SI_USER [pid: 0, uid: 0] stackpointer=0x523f0528 I get either a nice Java thread stack trace to standard error or a 300-megabyte core dump with no messages. I've been unable to reproduce the problem in any simplified test cases. So far, it happens only online with real client connections. Any tips on how I might get useful information from the core dumps? Is anyone successfully using Blackdown 1.3.1-02b-FCS (green threads, nojit) with the latest Red Hat Linux 7.0 Kernel and Glibc packages (Kernel 2.2.22, Glibc 2.2.4)? Would I be better off switching to the combination of Linux Kernel 2.4.18 and Glibc 2.2.4, as in Red Hat Linux 7.2? I guess I'm curious which kernel and library versions are getting the most testing by Blackdown developers among all these combinations, shown with their latest updated version numbers: Red Hat Kernel Glibc --- -- -- 6.22.2.22 2.1.3 7.02.2.22 2.2.4 7.12.4.18 2.2.4 7.22.4.18 2.2.4 7.32.4.18 2.2.5 8.02.4.18 2.2.93 Thanks, John Neffenger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Segmentation violation (even with ulimit -s 2048)
John, You can run "/usr/bin/strings core" to get some info from the core file. I have been doing Java development daily on a Mandrake 8.2 system for several months. Glibc version is 2.2.4, but I continuously move to the latest versions of the Blackdown JVM (currently 1.4.1 beta) so it's been a while since I've used 1.3.1 FCS. John Neffenger wrote: I had been running Blackdown 1.3.1-FCS (green threads, nojit) without any problems for over a year on a system with Linux Kernel version 2.2.16 and Glibc 2.2.4 on a Red Hat Linux 7.0 base. I've been using the "ulimit -s 2048" setting to avoid the problem that caused segmentation violations earlier in 2001 (Sun Bug Id 4466587). Now I've upgraded to all the very latest Red Hat Linux 7.0 updates: Blackdown 1.3.1-02b-FCS (green theads, nojit) kernel-2.2.22-7.0.2 glibc-2.2.4-18.7.0.7 The version strings for Blackdown and the kernel are: Classic VM (build Blackdown-1.3.1-02b-FCS, green threads, nojit) Linux www.volano.com 2.2.22-7.0.2 #1 Mon Sep 23 06:55:40 EDT 2002 i686 As before, I'm still setting: ulimit -s 2048 ulimit -n 1024 and I still start up Blackdown with the options "-green -Xmx256m -Xss64k". But now I'm getting daily segmentation violations on our server -- one or two per day: SIGSEGV 11* segmentation violation si_signo [11]: SIGSEGV 11* segmentation violation si_errno [0]: Success si_code [0]: SI_USER [pid: 0, uid: 0] stackpointer=0x523f0528 I get either a nice Java thread stack trace to standard error or a 300-megabyte core dump with no messages. I've been unable to reproduce the problem in any simplified test cases. So far, it happens only online with real client connections. Any tips on how I might get useful information from the core dumps? Is anyone successfully using Blackdown 1.3.1-02b-FCS (green threads, nojit) with the latest Red Hat Linux 7.0 Kernel and Glibc packages (Kernel 2.2.22, Glibc 2.2.4)? Would I be better off switching to the combination of Linux Kernel 2.4.18 and Glibc 2.2.4, as in Red Hat Linux 7.2? I guess I'm curious which kernel and library versions are getting the most testing by Blackdown developers among all these combinations, shown with their latest updated version numbers: Red Hat Kernel Glibc --- -- -- 6.22.2.22 2.1.3 7.02.2.22 2.2.4 7.12.4.18 2.2.4 7.22.4.18 2.2.4 7.32.4.18 2.2.5 8.02.4.18 2.2.93 Thanks, John Neffenger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Matthew Avery Senior Developer (513) 470-5316 http://www.einnovation.com/ eInnovation, Inc., located in the heart of the midwest, invents and promotes eBusiness software that moves business technology to open standards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: running java on rh 8.0
All I had to do was change my PATH setting so that the 1.4.1 version of Java came before the libgcj one. I haven't tested everything yet, but so far, so good... Tom On Mon, 2002-11-04 at 17:15, Joseph Shraibman wrote: > I tried to run java 1.4.1 from sun on my rh 8.0 box and I spent a day trying to >figure out > why rmi wouldn't work. I finally figured out that I had to uninstall libgcj (which >was > needed by gettext, so I had to uninstall that too) and now everything works >perfectly. > I'm just posting this to help anyone else who may be having the same problem. >Perhaps > something could be done about this on the jdk side, I don't know. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: running java on rh 8.0
I figured it out. I was running the right *java*, but I was running the rmiregistry from libgcj. Tom Ball wrote: All I had to do was change my PATH setting so that the 1.4.1 version of Java came before the libgcj one. I haven't tested everything yet, but so far, so good... Tom On Mon, 2002-11-04 at 17:15, Joseph Shraibman wrote: I tried to run java 1.4.1 from sun on my rh 8.0 box and I spent a day trying to figure out why rmi wouldn't work. I finally figured out that I had to uninstall libgcj (which was needed by gettext, so I had to uninstall that too) and now everything works perfectly. I'm just posting this to help anyone else who may be having the same problem. Perhaps something could be done about this on the jdk side, I don't know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Joseph Shraibman [EMAIL PROTECTED] Increase signal to noise ratio. http://xis.xtenit.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
