[news.eclipse.platform] Re: Where is my JFrame? (was Strange behavior wh

["Yaron Reinharts" <yaronrein@xxxxxxxxxxx>]

Thank you Alexandros

I don't see this thread in the debug window
I see other threads, there are all seems to be running (including one which 
is called AWT-Shutdown)
I'm using Eclipse Version 3.3.1

Anyway, I found a workaround for my problem (skipping the console reading)
However, I'm still curious to understand what happened and to know if I 
should do something about it (bug report)

Thanks
/Yaron

"Alexandros Karypidis" <akarypid@xxxxxxxx> wrote in message 
news:47429F85.3040509@xxxxxxxxxxx
> If you debug your application, you'll see that if you interrupt the main 
> thread you'll see it's within:
>
> WDesktopProperties.init() line: not available [native method]
> whereas the other thread is
>
> FileInputStream.readBytes(byte[], int, int) line: not available [native 
> method]
> My guess is that the Swing library somehow accesses the console in 
> WDesktopProperties.init() causing a deadlock. I'd use an object to wait 
> for the frame to become visible before proceeding with console access:
>
> public void run() {
> synchronized (sync) {
> try {
> sync.wait();
> } catch (InterruptedException e) {
> return;
> }
> }
> // ...
>
> and
>
> private WhereIsMyJFrame() {
> // ...
> JFrame frame = new JFrame("WhereIsMyJFrame");
> synchronized (sync) {
> sync.notify();
> }
> System.out.println("main window created");
> frame.setVisible(true);
>
> Also, I'd guess that you could reproduce this thing outside of Eclipse if 
> you ran your program from the command line and redirected your standard 
> input and output.