This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 41886 - [JDK1.5] Crash during launch under JDK 1.5.0 beta1 on AMD64 (64bit mode)
Summary: [JDK1.5] Crash during launch under JDK 1.5.0 beta1 on AMD64 (64bit mode)
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: issues@platform
URL:
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2004-04-09 14:00 UTC by lynggaard
Modified: 2008-12-22 19:48 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The error log gererated by the VM during the crash (12.74 KB, text/plain)
2004-04-09 14:02 UTC, lynggaard
Details
Another error log (13.89 KB, text/plain)
2004-04-09 14:03 UTC, lynggaard
Details
another error log (trying interpreted mode instead of mixed mode) (12.67 KB, text/plain)
2004-04-09 14:04 UTC, lynggaard
Details
yet another crash (13.89 KB, text/plain)
2004-04-09 14:05 UTC, lynggaard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lynggaard 2004-04-09 14:00:24 UTC
I have the following setup:

* Gentoo Linux
* Java: Linux AMD64 RPM in self-extracting file 
(j2sdk-1_5_0-beta-linux-amd64-rpm.bin)
* Netbeans 3.6 rc3

The problem:
Each time I try to start Netbeans it crahes, or
more specificly the JVM crashes, giving me a 

#
# An unexpected error has been detected by HotSpot
Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x0000002ae4c008f0,
pid=7194, tid=1076623728
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM
(1.5.0-beta-b32c mixed mode)

Note: I have reported this on the java bug parade
earlier, but they told me to log it here since you
could better pinpoint the probleam
Comment 1 lynggaard 2004-04-09 14:02:06 UTC
Created attachment 14339 [details]
The error log gererated by the VM during the crash
Comment 2 lynggaard 2004-04-09 14:03:47 UTC
Created attachment 14340 [details]
Another error log
Comment 3 lynggaard 2004-04-09 14:04:57 UTC
Created attachment 14341 [details]
another error log (trying interpreted mode instead of mixed mode)
Comment 4 lynggaard 2004-04-09 14:05:28 UTC
Created attachment 14343 [details]
yet another crash
Comment 5 lynggaard 2004-04-09 14:09:26 UTC
As you can see from the attachment it is very reproduceable, in fact I
have never gotten it to start right

If I recall correctly when I tried this on an earlier Netbeans 3.6 RC
I think i could get it to start if I added the -verbose flag, but it
would crash soon after starting. I have tested that trick under RC3
but no luck,

I have also got the blackdown 1.4.2_rc1 64bit java vm on my system,
and it works fine with netbeans.

Please let me know if there is any workaround I should test

Comment 6 Marian Mirilovic 2004-04-09 14:31:51 UTC
I am sorry but we con do nothing for you, if JVM crashes it's bug of
JVM, please file issue against JDK.

BTW: you are using beta build of not promoted JDK (1.5.0) - it measn
it still isn't so stable and it seems like it's really old build (
1.5.0-beta-b32c ), please try the newer one .

Thanks in advance.
Comment 7 lynggaard 2004-04-09 15:23:50 UTC
This sucks :-\

I file the bug in sun's bugparade, and they reject the bug and tell me
to file it here because you would be better at pinpointing the problem.

I file it here (AS SUGGESTED BY THE JVM PEOPLE!!) and you say not our
problem go talk to the jvm people.

BTW: AFAIK there are no newer builds publically available I can only
find the beta 1

I am reopening this bug as I was told to file it here.I will also
resubmit it to the JVM people, and put the bug id into this report.

Please inform me on how to obtain a newer build of jdk 1.5, so that I
may test it as suggested.
Comment 8 Marian Mirilovic 2004-04-09 15:42:05 UTC
Ok,
can you provide bug number from BugParade?

If you are not SUN INTERNAL, you haven't access to newer JDK1.5.0
build :( , so wait for public beta2...

I still don't think it's our problem, but let this issue open - for
evaluation ...

Have you tried run another java application on your JDK1.5.0beta1 ?

Thanks for help...
Comment 9 _ ttran 2004-06-14 13:00:51 UTC
we can't fix it on our side. Better to wait for another beta from JDK 
Comment 10 Marian Mirilovic 2005-07-15 07:52:51 UTC
closed