Re: Thread.yield() on 2.4 - more

2001-02-09 Thread Juergen Kreileder
> "Dimitris" == Dimitris Vyzovitis <[EMAIL PROTECTED]> writes: Dimitris> On 9 Feb 2001, Juergen Kreileder wrote: >> BTW, it's "Thread.yield()". "Thread.currentThread().yield()" >> has exactly the same meaning but as Thread.yield() is a class >> method you should call it direc

Does jdb work on linux?

2001-02-09 Thread Joi Ellis
I've tried off and on for the last six months to get any app running under jdb. I'm familiar with gdb, and I've studied jdb's help and the debugger section of 'Core Java' but it simply doesn't fly. Do any jdb variants actually run on linux? Can anyone provide a simple working example of launchi

Re: Messed up swing windows

2001-02-09 Thread Miloslaw Smyk
Hi! Joi Ellis wrote: > I am a linux geek and I regularly see this sort of behavior in apps > written by inexperienced Java developers running windows. It seems that > the heavyweight peers behave differently between *nix and Windows. Some > actions which are separate method calls in Java are

Re: Messed up swing windows

2001-02-09 Thread Joi Ellis
On Sat, 10 Feb 2001, Miloslaw Smyk wrote: > Hi! > > Yeah, one revalidate() call fixed it. Thanks! Cool! > And BTW, we do a lot of testing (and major part of development) on Linux, > but in this particular case we assumed that GUI code generated by IBM's > VisualAge was OK. Wrongly, as it turne

Re: Thread.yield() on 2.4 - more

2001-02-09 Thread Dimitris Vyzovitis
On 9 Feb 2001, Juergen Kreileder wrote: > BTW, it's "Thread.yield()". "Thread.currentThread().yield()" has > exactly the same meaning but as Thread.yield() is a class method you > should call it directly on the class. > "Thread.currentThread().yield()" makes it look like yield() would be > an in

RE: Messed up swing windows

2001-02-09 Thread Robert S Laramee
> > Make sure you are not mixing up light weight and heavy weight Java > > components. There's a tutorial on this from www.javasoft.com > > If my understanding of light weight vs heavy weight is correct, it means > awt components vs swing Jcomponents. This should not be a problem as I > don't us

Re: Thread.yield() on 2.4 - more

2001-02-09 Thread Juergen Kreileder
> "Dimitris" == Dimitris Vyzovitis <[EMAIL PROTECTED]> writes: Dimitris> On Thu, 8 Feb 2001, Joseph Shraibman wrote: >> Is it just me or does Thread.yield() not work anymore with the >> 2.4.0 kernel? Dimitris> Interesting: blackdown jdk seems to indeed behave Dimitris> in

RE: Messed up swing windows

2001-02-09 Thread Martin, Stephen
> > Make sure you are not mixing up light weight and heavy weight Java > components. There's a tutorial on this from www.javasoft.com If my understanding of light weight vs heavy weight is correct, it means awt components vs swing Jcomponents. This should not be a problem as I don't use any swi

SIGSEGV with DB2 (java) client on Linux

2001-02-09 Thread Maarten Oelering
Hello, I sometimes get a SIGSEGV (segmentation violation) that crashes my JVM when calling the IBM DB2 JDBC driver. The problem occurs with both the IBM JDK and the Blackdown JDK. Both JDKs report a SIGSEGV 11* segmentation violation with the same stack trace: "Thread-5" (TID:0x402e7ae0, sys

Re: Thread.yield() on 2.4 - more

2001-02-09 Thread Dimitris Vyzovitis
On Thu, 8 Feb 2001, Joseph Shraibman wrote: > Is it just me or does Thread.yield() not work anymore with the 2.4.0 > kernel? Interesting: blackdown jdk seems to indeed behave incorrectly. Sample execution of the test program I posted previously (I am on an smp box with two processors, so the ca