Bug 28811

Description David Soroko 2002-12-22 19:23:13 EST

Eclipse crashes while in debug session, executing a "step into".
The platform is Linux Redhat 8.0

Here is the content of the .log file:

!SESSION Dec 22, 2002 11:54:07.613 ---------------------------------------------
java.version=1.4.1_01
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -install
file:/home/xor/devtools/eclipse/
!ENTRY org.eclipse.ui 4 4 Dec 22, 2002 11:54:07.614
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Dec 22, 2002 11:54:07.616
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
	at
org.eclipse.ui.internal.dialogs.FontPreferencePage.performApply(FontPreferencePage.java:590)
	at
org.eclipse.jface.preference.PreferencePage$2.widgetSelected(PreferencePage.java:264)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:87)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:868)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1456)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1278)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:561)
	at org.eclipse.jface.window.Window.open(Window.java:541)
	at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:47)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:769)
	at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:411)
	at
org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:365)
	at
org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:356)
	at
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:48)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:868)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1456)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1278)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1446)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1429)
	at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
	at org.eclipse.core.launcher.Main.run(Main.java:703)
	at org.eclipse.core.launcher.Main.main(Main.java:539)


And this is what is seen on the command prompt:

Xlib: unexpected async reply (sequence 0x9a8bc)!
Xlib: unexpected async reply (sequence 0x9a8d9)!
Xlib: unexpected async reply (sequence 0x9a8da)!
Xlib: unexpected async reply (sequence 0x9a8dc)!
Xlib: unexpected async reply (sequence 0x9a8dd)!
Xlib: unexpected async reply (sequence 0x9ab69)!
Xlib: unexpected async reply (sequence 0x9ab6a)!
Xlib: unexpected async reply (sequence 0x9ab6c)!
Xlib: unexpected async reply (sequence 0x9ab6d)!
Xlib: unexpected async reply (sequence 0x9ab8a)!
Xlib: unexpected async reply (sequence 0x9ab8b)!
Xlib: unexpected async reply (sequence 0x9ab8d)!
Xlib: unexpected async reply (sequence 0x9ab8e)!
Xlib: unexpected async reply (sequence 0x9abab)!
Xlib: unexpected async reply (sequence 0x9abac)!
Xlib: unexpected async reply (sequence 0x9abae)!
Xlib: unexpected async reply (sequence 0x9abaf)!
Xlib: unexpected async reply (sequence 0x9acaf)!
The program '<unknown>' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 635302 error_code 9 request_code 62 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)