The debugger output shall be visible on the calling console.
Could you please specify an environment variable prior to IDB call:
$ export GDK_NATIVE_WINDOWS=1
What does the following issue on the console where you start the debugger:
$ java -version
Which is the compiler package you installed (latest update is l_cprof_p_11.1.072)?
Regards,
Hubert.
Problem with starting intel debugger and file not found
如需更全面地了解编译器优化，请参阅优化注意事项.
- 登录以发表评论
星期二, 04/05/2010 - 03:12
- 登录以发表评论
星期二, 04/05/2010 - 19:18
Hi Hubert,
I tried the export command but it still doesn't work.
Running the command gives:
taywb@cluster:~/Ocean/TIMCOM_MULTI> java -version
java version "1.6.0_20"
Java SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot 64-Bit Server VM (build 16.3-b01, mixed mode)
taywb@cluster:~/Ocean/TIMCOM_MULTI> which java
/home/taywb/codes/jre1.6.0_20/bin/java
Is there any other solution?
Thank you!
Regards
- 登录以发表评论
星期二, 04/05/2010 - 21:10
Hi,
I was using SSH secure shell. Now I used putty and it works. The missing file msg still appears though.
Thanks
- 登录以发表评论
星期三, 05/05/2010 - 02:39
So does this mean that the graphics issues are gone wich using Putty?
Re: "Unable to locate source file "/usr/src/packages/BUILD/glibc-2.3/sysdeps/i386/elf/start.S" ..."
This is kind of a startup bug that is seen sometimes, especially on platforms/distros that are not fully validated.
Just click 'No' on the dialog and continue regular debugging. Please let me know if this helps or if you encounter other debugger issues(such as some GUI dialogs not working or so). The GDK workaround ($ export GDK_NATIVE_WINDOWS=1) I told you helps in any case where an older Eclipse is on the system.
Regards,
Hubert.
- 登录以发表评论
星期三, 05/05/2010 - 19:18
Hi Hubert,
Yes, the problem is gone when using putty.
Thanks for your help.
Regards
Problem with starting intel debugger and file not found
Hi,
I just installed the intel fortran compiler for linux on SUSE LINUX Enterprise Server 9 (x86_64). I followed the instructions to update my java as well.
However running "idb" gives:
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(:12417): Gdk-CRITICAL **: file gdkscreen-x11.c: line 122 (gdk_screen_get_display): assertion `GDK_IS_SCREEN (screen)' failed
(:12417): Gdk-CRITICAL **: file gdkscreen-x11.c: line 122 (gdk_screen_get_display): assertion `GDK_IS_SCREEN (screen)' failed
(:12417): Gdk-CRITICAL **: file gdkdisplay.c: line 462 (gdk_display_get_pointer): assertion `GDK_IS_DISPLAY (display)' failed
(:12417): Gdk-CRITICAL **: file gdkdisplay.c: line 462 (gdk_display_get_pointer): assertion `GDK_IS_DISPLAY (display)' failed
(:12417): Gdk-CRITICAL **: file gdkscreen.c: line 160 (gdk_screen_get_monitor_at_point): assertion `GDK_IS_SCREEN (screen)' failed
(:12417): Gdk-CRITICAL **: file gdkscreen.c: line 160 (gdk_screen_get_monitor_at_point): assertion `GDK_IS_SCREEN (screen)' failed
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(:12417): Gdk-CRITICAL **: file gdkscreen-x11.c: line 339 (gdk_screen_get_n_monitors): assertion `GDK_IS_SCREEN (screen)' failed
(:12417): Gdk-CRITICAL **: file gdkscreen-x11.c: line 339 (gdk_screen_get_n_monitors): assertion `GDK_IS_SCREEN (screen)' failed
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
(:12417): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
May I know what is the problem?
I also installed the same software on another system. I managed to get the GUI working. However, during start, it shows:
Unable to locate source file "/usr/src/packages/BUILD/glibc-2.3/sysdeps/i386/elf/start.S" ...
Is this a serious problem? What can I do?
Lastly, on another system running CentOS release 4.8 (Final), when I run "idb", it can start but there's an error msg:
(:17484): Gtk-WARNING **: Unable to locate theme engine in module_path: "bluecurve",
Is this a serious problem too?
Thanks alot!