On 1-Dec-08, at 10:32 PM, Lachlan Deck wrote:
> On 02/12/2008, at 4:46 PM, David Holt wrote:
>
>> The behaviour of WOLips immediately terminating an app I try to run
>> in development has returned over the weekend. This is really really
>> frustrating and seemingly random. I have no idea what is causing
>> the conflict with WOLips.
>>
>> I have included a little screenshot of the behaviour.
>>
>> Can anyone tell me where to find error messages in Eclipse? The
>> only one I have found is under Eclipse>About Eclipse
>> Platform...>Configuration Details>Show error log
>
> Same details but:
> Window > Show View > Other... > Error Log
Thanks. Much easier!
>
>
>> I don't think that it reveals anything helpful but could someone
>> confirm that when they start up an Eclipse session in 10.5.5 they
>> see the same thing? Nothing is added to the log when I try to run.
>> Is there another way to get error output that I am overlooking?
>>
>> It doesn't matter if I use Eclipse 3.3 or 3.4. Upgrade, downgrade
>> wolips. It will not run an application in development.
>>
>> A clean install on a new Leopard install works fine. Does anyone
>> have a clue what this could possibly be??
>
> Any problems showing in the Project(s)?
No, none at all.
>
>
>> David
>>
>> !SESSION 2008-12-01 21:22:24.184
>> -----------------------------------------------
>> eclipse.buildId=M20080911-1700
>> java.version=1.5.0_16
>> java.vendor=Apple Inc.
>> BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
>> Framework arguments: -keyring /Users/dholt/.eclipse_keyring -
>> showlocation
>> Command-line arguments: -os macosx -ws carbon -arch x86 -keyring /
>> Users/dholt/.eclipse_keyring -consoleLog -showlocation
>>
>> !ENTRY org.eclipse.core.net 1 0 2008-12-01 21:22:42.093
>> !MESSAGE System property http.nonProxyHosts has been set to local|
>> *.local|169.254/16|*.169.254/16 by an external source. This value
>> will be overwritten using the values from the preferences
>>
>> Trying a debug adds the following to the log:
>>
>> !ENTRY org.eclipse.jdt.launching 4 120 2008-12-01 21:26:23.776
>> !MESSAGE Cannot connect to VM
>> !STACK 0
>> java.net.SocketException: Socket closed
>> at java.net.PlainSocketImpl.socketAccept(Native Method)
>> at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>> at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>> at java.net.ServerSocket.accept(ServerSocket.java:421)
>> at
>> org
>> .eclipse
>> .jdi
>> .internal
>> .connect.SocketTransportService.accept(SocketTransportService.java:
>> 95)
>> at
>> org
>> .eclipse
>> .jdi
>> .internal
>> .connect.SocketTransportImpl.accept(SocketTransportImpl.java:56)
>> at
>> org
>> .eclipse
>> .jdi
>> .internal
>> .connect
>> .SocketListeningConnectorImpl
>> .accept(SocketListeningConnectorImpl.java:135)
>> at org.eclipse.jdt.internal.launching.StandardVMDebugger
>> $ConnectRunnable.run(StandardVMDebugger.java:107)
>> at java.lang.Thread.run(Thread.java:613)
>>
>> <terminate on run.mov>
>
> with regards,
> --
>
> Lachlan Deck
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Dec 02 2008 - 01:49:02 EST