Re: GWP doesn't compile (patch included)

[Daniel Burrows <Daniel_Burrows brown edu>]

On Sat, Dec 19, 1998 at 08:15:15PM -0500, sml13@cornell.edu scribbled:
> Yay, your patch let me compile!  But now I get a runtime error (I get 
> this with gmc and gnumeric and just about everything else too):
> 
> [shane@cx637332-a gnome]$ gwp  
> Win95 Theme Init
> gwp: error in loading shared libraries
> /usr/local/gnome/lib/libgnomeui.so.31: undefined symbol: 
> gdk_imlib_set_cache_info
> 
> Any patches for that one? :-)
> 

  I don't get this, I think you need update something.  Dunno what. :-)

  I do get the following, reliably:

Unable to connect to server port 35091
This generally means that the program could not talk to the esound server
gwpIO -- g_module_check_init called
C++ Plugin Wrapper -- g_module_check_init called
simple -- g_module_check_init called
wordcount -- g_module_check_init called
spelling checker -- g_module_check_init called
find -- g_module_check_init called
frame new scratch: frame=0x8093518 ss=0x80b7020
newPluginView called without being overloaded!
Gtk-Message: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
Segmentation fault

  Running it gdb reveals:

Program received signal SIGSEGV, Segmentation fault.
0x402b0b38 in gtk_widget_destroy (widget=0x80c5500) at gtkwidget.c:1375
1375      g_return_if_fail (GTK_IS_WIDGET (widget));
Current language:  auto; currently c
(gdb) backtrace
#0  0x402b0b38 in gtk_widget_destroy (widget=0x80c5500) at gtkwidget.c:1375
#1  0x400511a4 in gnome_app_remove_menus (app=0x80b4650, 
    path=0x8076f06 "Plugins/", items=400) at gnome-app-helper.c:1375
#2  0x8064499 in wp_frame_update_plugins_menu (frame=0x8093528)
    at wp_frame.C:696
#3  0x8064697 in wp_frame_create (document_name=0x0) at wp_frame.C:769
#4  0x80606b8 in main (argc=1, argv=0xbffffc44) at wp.C:129

  I poked around in the gnome_app_remove_menus() code and discovered that
it calls gtk_container_remove() on each menu item, followed by
gtk_destroy_widget(), but the gtk_destroy_widget() segfaults first time.  Is
it possible that gtk_container_remove() destroys the widget, causing
gtk_destroy_widget() to free() memory which has already been deallocated, or
something like that?  Anyway, this looks like maybe a libgnomeui bug.. (?)

-- 
  Daniel Burrows

  Nothing is hopeless.

  PROOF:
(a) Assume the opposite.
(b) If something _is_ hopeless, then its condition can only improve.
(c) If its condition can only improve, then there must be hope for it.
(d) Therefore, nothing is hopeless.  QED.

PGP signature