instant crash in guile-gtk on RS6000 running AIX4.3

[Daniel Ortmann <ortmann at vnet dot ibm dot com>]

I've installed the following:
glib-1.2.6
gtk+-1.2.6
guile-1.3.4
guile-gtk-0.17
guile-oops-0.1.6

Segmentation violation instantly when running:
---------------------------------------------
neon:examples$ xldb /tmp/.ortmann/GUILE/bin/guile-gtk-1.2 -s test-gtk.scm 

Stack backtrack:
---------------
scm_register_module_xxx()
sgtk_register_glue()
inner_main()
invoke_main_func()
scm_internal_lazy_catch()
scm_boot_guile_1()
scm_boot_guile()
main()
__start()


Locals for sgtk_register_glue() in guile-gtk.c:
----------------------------------------------
full_name: "gtk %static-initfuncs% sgtk_init_gtk_gtk_glue"
func: @2FF2097C
name: "sgtk_init_gtk_gtk_glue"
modprefix: []

Note that when I tried to view the stack frame for scm_register_module_xxx()
itself I saw nothing intelligible.  Hence I give you the sgtk_register_glue()
frame instead.  I suspect someting is incompatible with the code line marked
below.

Even though I have guile-1.3.4 installed, guile-gtk appears to only build
guile-gtk-1.2 for some reason.  :-/


Earlier I had received either a compiler error or warning at the "XXX" line
marked below.  Since then the error or warning has disappeared.  Sorry.  :-/

-------------------------------------------------------------------
void
sgtk_register_glue (char *name, void (*func)(void))
{
  static char modprefix[] = "gtk %static-initfuncs% ";
  char *full_name;

  full_name = malloc (strlen (name) + sizeof (modprefix) + 1);
  if (full_name == NULL)
    return;

  strcpy (full_name, modprefix);
  strcat (full_name, name);
  scm_register_module_xxx (full_name, func);  /* XXX */
}


Please cc: me on responses.  I don't subscribe to this list.

Thank you.

-- 
Daniel Ortmann, IBM Circuit Technology, Rochester, MN 55901-7829
ortmann@vnet.ibm.com or ortmann@us.ibm.com and 507.253.6795 (external)
ortmann@rchland.ibm.com and tieline 8.553.6795 (internal)
ortmann@isl.net and 507.288.7732 (home)

"The answers are so simple, and we all know where to look,
but it's easier just to avoid the question." -- Kansas