RE: Netbeans?
> Hi, > Has anybody tried to use netbeans in linux? Yep. > It is a promising IDE, but with a slight problem : It hangs when you try > to create a new class (for eg). And randomly when editing code - at least it here it does. Anyway, let me guess, you enter the class name and press enter, right? If so, don't press enter, use the mouse and click OK. That fixed the same problem for me - at least under Beta 1. > I wouldn't like to admit it, but it runs normally under nt (...) :( That means the "problem" won't be fixed, not by Netbeans anyway. I guess the chances of me buying it are rather slim then... / Peter Schuller PGP signature
Re: problems with finalize()
[EMAIL PROTECTED] wrote: > [EMAIL PROTECTED] wrote ([EMAIL PROTECTED]) > > Hello, > > > > I have a problem with jdk1.1.6v3a/glibc2. The problem is with > > the finalize() methods which does not get invoked in my code. > > Jdk1.1.5v7/glibc2 works fine (ie. the finalize() method is called). > > Anyone got any idea why? > > (I tried to create a small example which shows the problem > > but finalize() get's called for the small example:( > > Some additional information might be in order.. > I force the finalizers to be run using System.runFinalizersOnExit(true) > so I expect that, even though finalization might not run immediately, > it should run when the VM exits.. > > Marcel > -- > "Yields falsehood when preceded by its quotation" > yields falsehood when preceded by its quotation Try running System.gc() after all references to the object are null. This should force the finalizer to run. hopr this helps Peter Johnson [EMAIL PROTECTED]
Re: Compilation hardware
Stefaan A Eeckels wrote: > I have a dual PII-266 (Intel Dakota, with 128Mb and SCSI disks > and I compile the Linux kernel in about 7 minutes, honest). How long does it take if you disable one CPU? What speed disks (7200RPM?) are you using? - Dan
Re: Evaluation license key for ORBacus Names
thanks for the consideration, but i dont give out personel info to marketeers, i'll try to do as much as i can to figure out whats wrong without the license gat Subject: Alpha-Linux JDK115 error Resent-Date: Sat, 29 Aug 1998 11:18:34 -0400 Resent-From: [EMAIL PROTECTED] Date: Sat, 29 Aug 1998 10:59:52 -0400 From: [EMAIL PROTECTED] (Rich Edwards) Organization: Codonics, Inc. To: java-linux <[EMAIL PROTECTED]> Uncle George - I'm having a problem with jdk115 (v10) when attempting to run InstallShield java setup programs. I've tried a couple of different ones, but the one shown below is from trying to install OOC's ORBacus Names product (www.ooc.com). It looks like it may be a bug related to 32 vs. 64-bit pointers. Any ideas? Thanks in advance, Rich Edwards - captured session start --- $ java setup InstallShield Java (TM) Edition Extracting installation codedone Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-dt-interface user-medium-r-normal-s*-*-*-*-*-*-*-*-*" to type FontSet Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-dt-interface user-medium-r-normal-s*-*-*-*-*-*-*-*-*" to type FontSet java: ../../../../src/genunix/java/green_threads/src/dl-malloc.c:1203: do_check_chunk: Assertion `(char*)p >= sbrk_base' failed. SIGABRT 6* abort (generated by abort(3) routine) Full thread dump: "AWT-Motif" (TID:0x1f21c10, sys_thread_t:0x15557adddb0, state:CW) prio=5 java.lang.Thread.run(Thread.java) "AWT-Input" (TID:0x1f21c50, sys_thread_t:0x15557abbdb0, state:R) prio=5 "AWT-EventQueue-0" (TID:0x1f217b0, sys_thread_t:0x1657db0, state:CW) prio=5 java.lang.Object.wait(Object.java) java.awt.EventQueue.getNextEvent(EventQueue.java:119) java.awt.EventDispatchThread.run(EventDispatchThread.java:55) "Finalizer thread" (TID:0x1f1bbc0, sys_thread_t:0x1635db0, state:CW) prio=1 "Async Garbage Collector" (TID:0x1f1bba0, sys_thread_t:0x1613db0, state:CW) prio=1 "Idle thread" (TID:0x1f1b690, sys_thread_t:0x15f1db0, state:R) prio=0 "Clock" (TID:0x1f14110, sys_thread_t:0x15cfdb0, state:CW) prio=12 "main" (TID:0x1f14160, sys_thread_t:0x1201bbaf0, state:R) prio=5 *current thread* sun.awt.motif.MComponentPeer.initialize(MComponentPeer.java:78) sun.awt.motif.MTextAreaPeer.initialize(MTextAreaPeer.java:71) sun.awt.motif.MComponentPeer.(MComponentPeer.java:126) sun.awt.motif.MTextAreaPeer.(MTextAreaPeer.java:75) sun.awt.motif.MToolkit.createTextArea(MToolkit.java:106) java.awt.TextArea.addNotify(TextArea.java:174) java.awt.Container.addNotify(Container.java:1128) java.awt.Panel.addNotify(Panel.java:77) java.awt.Container.addNotify(Container.java:1128) java.awt.Panel.addNotify(Panel.java:77) java.awt.Container.addNotify(Container.java:1128) java.awt.Panel.addNotify(Panel.java:77) java.awt.Container.addNotify(Container.java:1128) java.awt.Window.addNotify(Window.java:108) java.awt.Dialog.addNotify(Dialog.java:129) java.awt.Window.pack(Window.java:122) installshield.jshield.runtime.InfoContainer.toString(InfoContainer.java:206) setup.showGUI(install.java:259) setup.(install.java:247) setup.main(install.java:438) Monitor Cache Dump: java.lang.Object@llector": owner "main" (0x1201bbaf0, 4 entries) sun.awt.motif.MToolkit@r": owner "main" (0x1201bbaf0, 1 entry) Waiting to be notified: "AWT-Motif" (0x15557adddb0) (0x1613db0): Waiting to be notified: "Async Garbage Collector" (0x1613db0) java.awt.EventQueue@ctor": Waiting to be notified: "AWT-EventQueue-0" (0x1657db0) (0x17ffbf8): owner "main" (0x1201bbaf0, 1 entry) Registered Monitor Dump: Verifier lock: Thread queue lock: Name and type hash table lock: String intern lock: JNI pinning lock: JNI global reference lock: BinClass lock: Class loading lock: Java stack lock: Code rewrite lock: Heap lock: Has finalization queue lock: Finalize me queue lock: Waiting to be notified: "Finalizer thread" (0x1635db0) Monitor IO lock: Child death monitor: Event monitor: I/O monitor: owner "AWT-Input" (0x15557abbdb0, 1 entry) Alarm monitor: Waiting to be notified: "Clock" (0x15cfdb0) Monitor registry: owner "main" (0x1201bbaf0, 1 entry) Thread Alarm Q: sys_thread_t 0x1613db0 [Timeout in 78 ms] sys_thread_t 0x15557adddb0 [Timeout in 81 ms] sys_thread_t 0x15557abbdb0 [Timeout in 231 ms] Abort - captured s
Re: Compilation hardware
On 29-Aug-98 Dan Kegel wrote: > Stefaan A Eeckels wrote: > > I have a dual PII-266 (Intel Dakota, with 128Mb and SCSI disks > > and I compile the Linux kernel in about 7 minutes, honest). > > How long does it take if you disable one CPU? What speed > disks (7200RPM?) are you using? Two 4.5G Quantum UW drives, 7200rpm. I haven't timed the compilation with one CPU - I recompiled the kernel with SMP support and haven't had one problem since. Stefaan -- PGP key available from PGP key servers (http://www.pgp.net/pgpnet/) ___ Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. -- Saint-Exupéry
Re: Compilation hardware
On Sat, 29 Aug 1998, Stefaan A Eeckels wrote: > > On 29-Aug-98 Dan Kegel wrote: > > Stefaan A Eeckels wrote: > > > I have a dual PII-266 (Intel Dakota, with 128Mb and SCSI disks > > > and I compile the Linux kernel in about 7 minutes, honest). > > > > How long does it take if you disable one CPU? What speed > > disks (7200RPM?) are you using? > Two 4.5G Quantum UW drives, 7200rpm. I haven't timed the > compilation with one CPU - I recompiled the kernel with > SMP support and haven't had one problem since. I believe that if you compile with make -j1, it will be almost like compiling on a single-CPU system. Compiling with make -j2 should utilize both processors.
Re: final vs const
Gao Lei wrote:
Hi, guys,
I have a question during my developing,
In Java it is very easy to assign different final value sto different
instances of an object, but when in C ++, it is difficult, especially
for an array. Like following,
class CPPCls
{
const int iarray[10];
...
}
How to initialize this const array within C++?
Thanks in advance.
Gao Lei.
Well, if you are interested in initializing a const array with C++,
you should consider somehting like
const int array[] = {
0,
1,
//
9
};
I suggest that you leave out of a member fuinction declaration (ie make
it global , although it doesn't sound cool!) since the usual C++ compilers
complain about it!
I hope this would help.
Dimitrios
--
Dimitrios Vyzovitis
Information Processing Laboratory
Aristotle University of Thessaloniki
[EMAIL PROTECTED] or [EMAIL PROTECTED]
http://egnatia.ee.auth.gr/~dviz
begin: vcard
fn: Dimitrios Vyzovitis
n: Vyzovitis;Dimitrios
org:AUTH
adr:142 V. Olgas Avenue;;;Thessaloniki;;54645;Greece
email;internet: [EMAIL PROTECTED]
tel;work: ++30-31-996359
tel;home: ++30-31-817780
note: Orientation in space and time is the framework of cognition.
x-mozilla-cpt: ;0
x-mozilla-html: TRUE
version:2.1
end:vcard
Re: Netbeans?
Hi, > And randomly when editing code - at least it here it does. > > Anyway, let me guess, you enter the class name and press enter, right? If so, > don't press enter, use the mouse and click OK. That fixed the same problem for > me - at least under Beta 1. > Well, it behaves better (sometimes ;-} ) in this way, but I should call it at least UNSTABLE. Seriously, it doesn't behave like a beta version, but like an early preview release (at least in Linux). > > > I wouldn't like to admit it, but it runs normally under nt (...) > > :( That means the "problem" won't be fixed, not by Netbeans anyway. I guess > the chances of me buying it are rather slim then... Then I should leave my hopes for a serious IDE in freebuilder (it is also unstable, but it is not called beta2, but release 0.70) -- Dimitrios Vyzovitis Information Processing Laboratory Aristotle University of Thessaloniki [EMAIL PROTECTED] or [EMAIL PROTECTED] http://egnatia.ee.auth.gr/~dviz begin: vcard fn: Dimitrios Vyzovitis n: Vyzovitis;Dimitrios org:AUTH adr:142 V. Olgas Avenue;;;Thessaloniki;;54645;Greece email;internet: [EMAIL PROTECTED] tel;work: ++30-31-996359 tel;home: ++30-31-817780 note: Orientation in space and time is the framework of cognition. x-mozilla-cpt: ;0 x-mozilla-html: TRUE version:2.1 end:vcard
RE: Netbeans
Hi, This sounds like the TextField bug problem in the Blackdown Jitterbug bug database. This problem does not exist under the PowerPC JDK (at least I haven't seen it yet). Have your tried Juergen's trick of forcing the pre loading libBrokenLocale.so in the invocation of java? Also, have you posted this bug to Netbeans. They have a support e-mail address and a web forum that they respond to things in. Thanks, Kevin
Bug 118: coredump on dispose
Anybody have any clue about this ? I'm also affected by this bug (1.1.5v3) and it is very painful - I just could not use modal dialogs. Any chances to get it fixed soon ?? Artur
Redhat 5.0 Setup
Would someone mind telling me the files I need to setup the JDK on Redhat. Also, if you wouldn't mind, when I install the "glib??" files (something like that) what is the tar command to force them to overwrite the older versions. Sorry for the trouble, and thanks. Steve
Re: problems with finalize()
peter johnson wrote ([EMAIL PROTECTED]) > [EMAIL PROTECTED] wrote: > > [EMAIL PROTECTED] wrote ([EMAIL PROTECTED]) > > > Hello, > > > > > > I have a problem with jdk1.1.6v3a/glibc2. The problem is with > > > the finalize() methods which does not get invoked in my code. > > > Jdk1.1.5v7/glibc2 works fine (ie. the finalize() method is called). > > > Anyone got any idea why? > > > (I tried to create a small example which shows the problem > > > but finalize() get's called for the small example:( > > > > Some additional information might be in order.. > > I force the finalizers to be run using System.runFinalizersOnExit(true) > > so I expect that, even though finalization might not run immediately, > > it should run when the VM exits.. > > Try running System.gc() after all references to the object are null. This > should force the finalizer to run. > hopr this helps I've tries this (have a seperate thread call System.gc() every 2 seconds. This same thread also runs System.runFinalization()) but it doesn't help. As my application depends on finalizers being run I'm stuck with jdk1.1.5 for now... Marcel Ammerlaan
Alpha-Linux JDK115 error
Uncle George - I'm having a problem with jdk115 (v10) when attempting to run InstallShield java setup programs. I've tried a couple of different ones, but the one shown below is from trying to install OOC's ORBacus Names product (www.ooc.com). It looks like it may be a bug related to 32 vs. 64-bit pointers. Any ideas? Thanks in advance, Rich Edwards - captured session start --- $ java setup InstallShield Java (TM) Edition Extracting installation codedone Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-dt-interface user-medium-r-normal-s*-*-*-*-*-*-*-*-*" to type FontSet Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-dt-interface user-medium-r-normal-s*-*-*-*-*-*-*-*-*" to type FontSet java: ../../../../src/genunix/java/green_threads/src/dl-malloc.c:1203: do_check_chunk: Assertion `(char*)p >= sbrk_base' failed. SIGABRT 6* abort (generated by abort(3) routine) Full thread dump: "AWT-Motif" (TID:0x1f21c10, sys_thread_t:0x15557adddb0, state:CW) prio=5 java.lang.Thread.run(Thread.java) "AWT-Input" (TID:0x1f21c50, sys_thread_t:0x15557abbdb0, state:R) prio=5 "AWT-EventQueue-0" (TID:0x1f217b0, sys_thread_t:0x1657db0, state:CW) prio=5 java.lang.Object.wait(Object.java) java.awt.EventQueue.getNextEvent(EventQueue.java:119) java.awt.EventDispatchThread.run(EventDispatchThread.java:55) "Finalizer thread" (TID:0x1f1bbc0, sys_thread_t:0x1635db0, state:CW) prio=1 "Async Garbage Collector" (TID:0x1f1bba0, sys_thread_t:0x1613db0, state:CW) prio=1 "Idle thread" (TID:0x1f1b690, sys_thread_t:0x15f1db0, state:R) prio=0 "Clock" (TID:0x1f14110, sys_thread_t:0x15cfdb0, state:CW) prio=12 "main" (TID:0x1f14160, sys_thread_t:0x1201bbaf0, state:R) prio=5 *current thread* sun.awt.motif.MComponentPeer.initialize(MComponentPeer.java:78) sun.awt.motif.MTextAreaPeer.initialize(MTextAreaPeer.java:71) sun.awt.motif.MComponentPeer.(MComponentPeer.java:126) sun.awt.motif.MTextAreaPeer.(MTextAreaPeer.java:75) sun.awt.motif.MToolkit.createTextArea(MToolkit.java:106) java.awt.TextArea.addNotify(TextArea.java:174) java.awt.Container.addNotify(Container.java:1128) java.awt.Panel.addNotify(Panel.java:77) java.awt.Container.addNotify(Container.java:1128) java.awt.Panel.addNotify(Panel.java:77) java.awt.Container.addNotify(Container.java:1128) java.awt.Panel.addNotify(Panel.java:77) java.awt.Container.addNotify(Container.java:1128) java.awt.Window.addNotify(Window.java:108) java.awt.Dialog.addNotify(Dialog.java:129) java.awt.Window.pack(Window.java:122) installshield.jshield.runtime.InfoContainer.toString(InfoContainer.java:206) setup.showGUI(install.java:259) setup.(install.java:247) setup.main(install.java:438) Monitor Cache Dump: java.lang.Object@llector": owner "main" (0x1201bbaf0, 4 entries) sun.awt.motif.MToolkit@r": owner "main" (0x1201bbaf0, 1 entry) Waiting to be notified: "AWT-Motif" (0x15557adddb0) (0x1613db0): Waiting to be notified: "Async Garbage Collector" (0x1613db0) java.awt.EventQueue@ctor": Waiting to be notified: "AWT-EventQueue-0" (0x1657db0) (0x17ffbf8): owner "main" (0x1201bbaf0, 1 entry) Registered Monitor Dump: Verifier lock: Thread queue lock: Name and type hash table lock: String intern lock: JNI pinning lock: JNI global reference lock: BinClass lock: Class loading lock: Java stack lock: Code rewrite lock: Heap lock: Has finalization queue lock: Finalize me queue lock: Waiting to be notified: "Finalizer thread" (0x1635db0) Monitor IO lock: Child death monitor: Event monitor: I/O monitor: owner "AWT-Input" (0x15557abbdb0, 1 entry) Alarm monitor: Waiting to be notified: "Clock" (0x15cfdb0) Monitor registry: owner "main" (0x1201bbaf0, 1 entry) Thread Alarm Q: sys_thread_t 0x1613db0 [Timeout in 78 ms] sys_thread_t 0x15557adddb0 [Timeout in 81 ms] sys_thread_t 0x15557abbdb0 [Timeout in 231 ms] Abort - captured session end --- -- Rich Edwards Senior Software Engineer Codonics, Inc. e-mail: [EMAIL PROTECTED]
Re: finalize() problems
Hi, Sun has some serious problems in the 1.1.X series with finalization. Basically the finalizer thread can hold locks and threads waiting to be finalized can hold locks and can be waiting for finalization. Obviously, this can easily result in deadlocks (the finalizer needs to wait to obtain a lock while the thread holding that lock is waiting to obtain a finalization queue lock). Sun knows that this is a serious problem, but to fix it given the way finalization is done under 1.1.X is not easy and so they decided to only include a fix in 1.2 (which we don't have access to yet). To prevent the deadlocks, in jdk116_v3 and higher, we have not allowed threads to wait in the finalization queue. Instead they just return false. This greatly slows down finalization but does not stop it (and prevents deadlocks!). If the finalizer queue is empty and finalize() is called, the finalization will be done. If you truly want your application to work well on *all* java platforms, please don't use the finalize() call to do almost anything! (even loading a class can be a problem since there is a class loading lock). At least until 1.2 is out and everybody is using it on all platforms. Our changes might be causing your problems (but they are fixing others, ie. the deadlocks that prevented many programs from launching at all). If you have a SMALL sample program that illustrates this problem, we would be happy to try and track down the specific problem and try to get all things working. Also, you might want to try checking the return value from finalize() to see if it needs to be called again. If you can generate a small sample java program, please submit it using the Blackdown bug database. Thanks, Kevin Hendricks Blackdown JDK porting team member -- Kevin B. Hendricks Associate Professor, Operations & Information Technology School of Business, College of William & Mary Williamsburg, VA 23187, [EMAIL PROTECTED] http://business.tyler.wm.edu
