|
|
|
|
Re: More than one instances of Eclipse running simultaneously on one workspace [message #176406 is a reply to message #171374] |
Tue, 06 January 2004 22:39 |
Eclipse User |
|
|
|
Originally posted by: John_Arthorne.oti.com_
A fix was added in 3.0 M4 that *should* work on all platforms. Let us
know if you have reproducible cases that suggest otherwise:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=38399
--
Alex Chapiro wrote:
> PS. It would be too strong to say that it works in a wrong way on all
> unix-based systems. Actually I didn't check it on AIX or Solaris.
>
> Alex Chapiro wrote:
>
>> It is easy to reproduce it on QNX machine: just run two times "qde &"
>> from one terminal (qde is a shell script that launches Eclipse). On
>> the box with RedHat 8.0 with Gnome or KDE I'm running now two Eclipses
>> 2.1.2 connected to one workspace. On 3.0 with RedHat 9.0 GTK I cannot
>> reproduce it, but my colleague who works with Eclipse in Linux
>> environment only, told me that it happened from time to time,
>> especially when he launched Run-Time workspace sessions.
>>
>> Darin Swanson wrote:
>>
>>> Alex,
>>>
>>> We are interested in this and we just tried to reproduce here and
>>> could not
>>> reproduce the problem.
>>> We were successfully locked out from starting a second Eclipse
>>> session on
>>> the same workspace. This was on the I200312161200 GTK build.
>>>
>>> Can you verify that you can still cause the problem on this build?
>>> Can you provide us with the exact steps for how you can reproduce the
>>> problem?
>>>
>>> Thanks
>>> Darins
>>>
>>> "Alex Chapiro" <achapiro@qnx.com> wrote in message
>>> news:brnqn4$er8$1@eclipse.org...
>>>
>>>> I found that there is opened a bug report about it long time ago. I was
>>>> wondering what is the current state of this bug? The problem still
>>>> exists for all unix-based OS (for 2.1.2 and 3.0M5). It seems to be
>>>> dangerous because it could lead to workspace corruption.
>>>
>>>
>>>
>>>
>>>
|
|
|
Powered by
FUDForum. Page generated in 0.03098 seconds