Eclipse-Europa Web-browser

[Mike Bowie]

Ken Yamada wrote:
>   I agree, Mike.
>   It was just a quick patch to see if it solves the problem, and I rewrote it.
>   I also created jdk15 version successfully (http://www.tydfam.jp/eclipse-europa-jdk15.tgz) that enables me to run JBossTools-2.0.0b3. 
>
>   I found a bug at org.eclipse.swt.widget.FileDialog.presetChooserDialog() as below which I have no idea to fix so far.  And supports of Java guru is very appreciated.
>
>   It certainly has a lot of bugs yet, and aggressive bug finding and fixing is appreciated.
>
>
> (jdk15 version, but jdk16 is the same.)
>    :                   :                      :
> # Java VM: Java HotSpot(TM) Server VM (1.5.0_12-p6-ken_03_sep_2007_16_38 mixed mode)
> # Problematic frame:
> # C  [libc.so.7+0x20924]  realpath+0x294
> #
>
> ---------------  T H R E A D  ---------------
>
> Current thread (0x48241180):  JavaThread "main" [_thread_in_native, id=1210061056]
>
> siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000000
>
> Registers:
> EAX=0x00000000, EBX=0x481ac818, ECX=0x480aeb6c, EDX=0x48201100
> ESP=0xbfbfbef0, EBP=0xbfbfcb98, ESI=0x6eb5c540, EDI=0x48241240
> EIP=0x480d1924, EFLAGS=0x00210246
>
> Top of Stack: (sp=0xbfbfbef0)
> 0xbfbfbef0:   48231400 41225407 4260eaf0 412e9c15
> 0xbfbfbf00:   48231408 000003b0 bfbfbf28 48118c7e
> 0xbfbfbf10:   48231400 6ebe4758 4260eaf0 40f73485
> 0xbfbfbf20:   48231400 41225407 00000002 0000001e
> 0xbfbfbf30:   08052d64 48226000 bfbfbf48 480a8160
> 0xbfbfbf40:   482268ba 481ac818 482268ba 41306954
> 0xbfbfbf50:   482268ba 000000a5 00000003 480a8160
> 0xbfbfbf60:   00000001 00000000 bfbfbf88 41306954 
>
> Instructions: (pc=0x480d1924)
> 0x480d1914:   ff ff 03 bd 84 f3 ff ff e9 78 fe ff ff 8b 45 0c
> 0x480d1924:   c6 00 2f c6 40 01 00 8d 46 01 80 7e 01 00 0f 84 
>
> Stack: [0xbfa00000,0xbfc00000),  sp=0xbfbfbef0,  free space=2031k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
> C  [libc.so.7+0x20924]  realpath+0x294
> C  [libswt-pi-gtk-3346.so+0x2f119]  Java_org_eclipse_swt_internal_gtk_OS_realpath+0x89
> j  org.eclipse.swt.internal.gtk.OS.realpath([B[B)I+0
> j  org.eclipse.swt.widgets.FileDialog.presetChooserDialog()V+166
> j  org.eclipse.swt.widgets.FileDialog.openChooserDialog()Ljava/lang/String;+82
> j  org.eclipse.swt.widgets.FileDialog.open()Ljava/lang/String;+24
> j  org.eclipse.datatools.connectivity.internal.ui.dialogs.EditDriverDialog.handleLocationBrowseButtonPressed()V+89
> j  org.eclipse.datatools.connectivity.internal.ui.dialogs.EditDriverDialog.access$600(Lorg/eclipse/datatools/connectivity/internal/ui/dialogs/EditDriverDialog;)V+1
> j  org.eclipse.datatools.connectivity.internal.ui.dialogs.EditDriverDialog$3.widgetSelected(Lorg/eclipse/swt/events/SelectionEvent;)V+4
> j  org.eclipse.swt.widgets.TypedListener.handleEvent(Lorg/eclipse/swt/widgets/Event;)V+1003
>
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j  org.eclipse.swt.internal.gtk.OS.realpath([B[B)I+0
> j  org.eclipse.swt.widgets.FileDialog.presetChooserDialog()V+166
> j  org.eclipse.swt.widgets.FileDialog.openChooserDialog()Ljava/lang/String;+82
> j  org.eclipse.swt.widgets.FileDialog.open()Ljava/lang/String;+24
> j  org.eclipse.datatools.connectivity.internal.ui.dialogs.EditDriverDialog.handleLocationBrowseButtonPressed()V+89
> j  org.eclipse.datatools.connectivity.internal.ui.dialogs.EditDriverDialog.access$600(Lorg/eclipse/datatools/connectivity/internal/ui/dialogs/EditDriverDialog;)V+1
> j  org.eclipse.datatools.connectivity.internal.ui.dialogs.EditDriverDialog$3.widgetSelected(Lorg/eclipse/swt/events/SelectionEvent;)V+4
> j  org.eclipse.swt.widgets.TypedListener.handleEvent(Lorg/eclipse/swt/widgets/Ev:
>      :                      :                      :
>
>
>   
>   
Ken,

That's fantastic... really impressive stuff!

Do you have steps to reproduce the chooser bug?  Does it occur in 
build's against both 1.5 and 1.6 or are you running a 1.5 build against 
a 1.6 JAVA_HOME?  (Or visa versa.)

It would be great if we could roll the 1.5 and 1.6 ports into one... it 
shouldn't be too tricky.  I'd start looking at it now myself, but... 
unfortunately I'm away from tomorrow evening until the 24th of this 
month and may not have Internet access during that time.  I've got my 
hands pretty full until I leave too, I'm afraid.

Dan's making some inroads on getting the port into eclipse-devel, so 
that should be good.  If anyone has tried (and perhaps succeeded) 
building under amd or 64 platforms, it would be great to know!  For some 
reason everything I have on hand is x86-32.

Cheers,

Mike.