On Thu, Jun 10, 2004 at 11:02:51AM -0400, Marc Heckmann wrote:
> On Wed, Jun 09, 2004 at 11:58:32PM -0700, Hui Huang wrote:
> > The segfault messages look benign - they are the implicit NULL checks
> > within JVM.
>
> I will have to do more extensive tests using blackdown with
Marc Heckmann <[EMAIL PROTECTED]> writes:
> On Wed, Jun 09, 2004 at 11:58:32PM -0700, Hui Huang wrote:
>> The segfault messages look benign - they are the implicit NULL
>> checks within JVM.
>
> But look at the following discussion, Andi Kleen one of the x86_64
> k
On Wed, Jun 09, 2004 at 11:58:32PM -0700, Hui Huang wrote:
> The segfault messages look benign - they are the implicit NULL checks
> within JVM.
But look at the following discussion, Andi Kleen one of the x86_64
kernel developers says that the kernel has been fixed not to log the
messages
Juergen Kreileder wrote:
HotSpot uses SIGSEGV internally. It does on x86 too, but the x86
kernel doesn't have a segfault logger, so you don't get these messages
there. IIRC there's no way to disable the x86_64 segfault logger
without recompiling the kernel.
Oh and when is 1.4
arate
machines with the same results. Here are some of the messages I get:
java[4508]: segfault at 0008 rip 002a98544a78 rsp 007fbfffc1d0
error 4
java[4520]: segfault at 0008 rip 002a9845f3c2 rsp 4148bf20
error 4
The same thing happens with Sun's SDK
Radu-Adrian Popescu <[EMAIL PROTECTED]> writes:
> The error codes come in groups of 1-4 at a time, and they're
> alternate.
>
> What's causing this ?
HotSpot uses SIGSEGV internally. It does on x86 too, but the x86
kernel doesn't have a segfault logger, so y
The segfault messages look benign - they are the implicit NULL checks
within JVM.
Did you see a hang or a crash (i.e. tomcat process is gone,
segfaults in kernel log don't count, they are handled by JVM)?
Is this on HT Xeon? I've heard 2.6.5 in FC2 is not stable (frequent
hang) but 2
h the same results. Here are some of the messages I get:
java[4508]: segfault at 0008 rip 002a98544a78 rsp 007fbfffc1d0
error 4
java[4520]: segfault at 0008 rip 002a9845f3c2 rsp 4148bf20
error 4
The same thing happens with Sun's SDK.
Kernel version
s 2.2.12-42
>
> > -Original Message-
> > From: Johan Vos [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, August 24, 2000 11:36 AM
> > To: TAZ Gravel, Emmanuel
> > Cc: [EMAIL PROTECTED]
> > Subject:Re: Segfault on Sparc20 with 1.2.2 RC4
> >
&g
Title: Segfault on Sparc20 with 1.2.2 RC4
I've installed RC4 of jdk-1.2.2 for sparc Linux. When I
try to do java -version I get:
SIGSEGV 11* segmentation violation
si_signo [0]: no signal
si_errno [0]: Success
si_code [0]: SI_USER [pid: 0, uid: 0]
and I need to kill -
Hi everyone,
when I try to write large text files the JDK stops writing after 6MByte
with a segfault. In my project I have extensive use of Swing and
multithreading. Maybe this is the reason why I can't reproduce this
error with a small test program.
I'am using JDK1.2.2-RC3 (nati
On 18-Jul-99 Calin Medianu (Operations) wrote:
[JDK1.2 pre-v1 segfaults on SuSE 6.1]
> Mine segfaults as well. I run Slackware and jdk1.2pre-v2 (glibc2.0)
> and everything else works fine.
I see. Did you try the pre-v2 on SuSE 6.1 or it was a pre-v1 like mine?
In the former case, can someone (m
> Hello,
> if I run java -Xrunhprof:cpu=times I get a segfault, same if I use
> cpu=old, anything works perfectly with cpu=samples.
>
> I have JDK1.2 on a SuSE 6.1. It's my system or this happens to everybody?
Mine segfaults as well. I run Slackware and jdk1.2p
On 15-Jul-99 Juergen Kreileder wrote:
[cpu:times segfaults]
> I haven't seen any segfaults with it.
Damn, I wonder mine segfaults then, I'm using a standard SuSE 6.1 and
everything else works perfectly.
I tried to remove the JIT, but it segfaults anyway.
Can anybody guess what's happening?
>
> Kontorotsui writes:
Kontorotsui> On 15-Jul-99 Juergen Kreileder wrote:
Kontorotsui> [cpu:times segfaults]
>> I haven't seen any segfaults with it.
>> Note that 'times' doesn't show cpu times with pre 1 & 2, it will work
>> with the next release.
Kontorotsui> Then,
>>>>> Kontorotsui writes:
Kontorotsui> If I run java -Xrunhprof:cpu=times I get a segfault,
Kontorotsui> same if I use cpu=old, anything works perfectly with
Kontorotsui> cpu=samples.
Kontorotsui> I have JDK1.2 on a SuSE 6.1. It's my system or
Hello,
if I run java -Xrunhprof:cpu=times I get a segfault, same if I use
cpu=old, anything works perfectly with cpu=samples.
I have JDK1.2 on a SuSE 6.1. It's my system or this happens to everybody?
---
Andrea "Kontorotsui" Controzzi - MALE Student of Computer Science
Ok, I am giving up on it...
Using JDK1.2 prev1 and v2, we ran in a strange problem.
Everytime an applet or application is started, whenever some awt stuff is used,
the whole JRE segfaults like this:
SIGSEGV 11* segmentation violation
stackpointer=0x417b3c98
Full thread dump Classic
Colleagues,
My code is now compiling on my RH5.2 box. I have
run "rpm -ivh urw-fonts-1.0-3.src.rpm" (as root) to
install the fonts and I ran:
% g++ -shared -o /usr/local/lib/libstdc++-libc6.0-1.so.2 -lm
%ldconfig
When I try to run my code (which is swing
intensive), I get a series of complain
Whenever I try to run a java app (jre 1.1.6 v5, I immediately get a segfault
error. I'm running RH5.0 with libstdc++2.8.0-8 and KDE. I'm able to use kaffe
1.0 with no problem.
I've tried:
1) moving libc.so.6 and libdl.so.2a to another directory (from the default
$JA
Hi Steve,
Being brave and foolhearty, I gave 1.1.6v1-test a try.
1. command line java/javac work just fine.
2. appletviewer segfaults (dump below).
3. jdb fails not being able to find libnet_g.so (which is present
for duty in /opt/java/lib/i686/green_threads.
The Particulars of my sys
Hello!
Using
java_dyn version "sbb:08/16/97-14:45"
I got a signal 11 error with this class. I´m writing a Java-Compiler for a
project at University (nothing special, about 20 people are doing the
same, just for education).
The ´Test12.class´ is buggy, because there is an ´aload´ missing
22 matches
Mail list logo
