Eclipse gtk? problem, a bug (and a workaround for Mandrake 9.1) [message #64814] |
Thu, 05 June 2003 23:11 |
Eclipse User |
|
|
|
Originally posted by: robin.rosenberg.s/k/c/dewire.kom
Hi,
I'm looking for takers for this bug. The candidates are MandrakeSoft, the
Gnome Project and the Eclipse Project.
The problem is that debugging Java programs stop sometimes, i.e. most
times. If a breakpoint is set it is most likely that I will not be able to
step or even resume, stop or any kind of action. If it works it often slow.
First my environment. Eclipse - any 2.1 series (and if my memory serves me
right any 2.0 version). Mandrake 9.1 and JDK 1.4.1_02 (or any other
version, although JDK 1.3 was less receptible).
With Mandrake 9.0 there is not problem except some slugginess. Now I like
8.1 better since I got X and swsuspm, networking etc to work nicely and it
has a newer KDE. Replacing some or fthe GTK libraties I could circument
the problem. I haven't told Murphy yet though.
I got these packages off the Mdk 9.0 disks and unpacked them in a
directory of their own.
libgdk_pixbuf2.0_0-2.0.6-8mdk
libgdk-pixbuf2-0.18.0-3mdk
libgdk-pixbuf-gnomecanvas1-0.18.0-3mdk
gdk-pixbuf-loaders-0.18.0-3mdk
libgtk+-x11-2.0_0-2.0.6-8mdk.i586.rpm
Finally I started eclipse:
# GDK_USE_XFT=0 LD_LIBRARY_PATH=/home/robin/gdk/usr/lib eclipse
(<unknown>:24241): Gtk-WARNING **: Kan inte hitta temamotorn i
"module_path": "galaxy",
Mandrake 9.1 contains these versions:
gdk-pixbuf-loaders-0.22.0-1mdk
libgdk-pixbuf2-0.22.0-1mdk
libgdk_pixbuf2.0_0-2.2.1-6mdk
libgdk-pixbuf-gnomecanvas1-0.22.0-1mdk
libgtk+-x11-2.0_0-2.2.1-2mdk
If someone has or wants to have a clue about what's going on I'll be
happy to supply more information.
-- robin
|
|
|
|
Re: Eclipse gtk? problem, a bug (and a workaround for Mandrake 9.1) [message #65242 is a reply to message #64957] |
Fri, 06 June 2003 09:43 |
Eclipse User |
|
|
|
Originally posted by: robin.rosenberg.dewire.com.INSERT.BEFORE.MAILING
Donatas Simkunas wrote:
> I experienced similar problem in GTK version, but it happens not every
> time. Whats intersting after break point hit, (when problem occurs)
> eclipse
> responses only to right mouse click.
>
You don't experience simuliar problems, you *experience* the exact same
problem. The right-clicking,as you mention, you mention is another
"feature" of the problem. I guess eclipse is actually doing something
sometimes without updating the screen. Well it is redrawing, but it looks
like cached double-buffered images, or something similar. Scrolling in the
debug (call stack) windows sometimes seem to scroll only a part of the
window. Events that are issues are executed later when the right mouse
button is pressed and eventually eclipse get totally stuck and "killall
java" is THE command.
-- robin
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03646 seconds