Re: guile-gnome-platform: segfault on exit

[gregory benison]

> FWIW, I can't reproduce this on Guile from stable-2.0.

FWIW, I can't, either :)  So maybe the moral of the story here is: use
guile >2.0.  However, I suspect that guile-1.8.x will be found in the
wild for quite some time to come.

One observation... if we look at this point in execution (frame "6" here):

#6  0xb788a3ac in scm_i_init_thread_for_guile (base=0xbfc25b24,
parent=0xb7511f20) at threads.c:600
#7  0xb788a4d4 in scm_i_with_guile_and_parent (func=0xb7844b8e
<really_cleanup_for_exit>, data=0x0, parent=0xb7511f20) at
threads.c:732
#8  0xb788a4aa in scm_with_guile (func=0xb7844b8e
<really_cleanup_for_exit>, data=0x0) at threads.c:721
#9  0xb7844bd8 in cleanup_for_exit () at init.c:398

at the start of scm_i_init_thread_for_guile() --

SCM_I_CURRENT_THREAD != NULL   *when*  guile >= 2.0
SCM_I_CURRENT_THREAD != NULL   *when*  guile=1.8.8 and (use-modules
(gnome gtk)) has _not_ been called
SCM_I_CURRENT_THREAD == NULL  *when* guile=1.8.8 and (use-modules
(gnome gtk)) has been called (then segfault)

i.e. calling (use-modules (gnome gtk)) somehow causes
SCM_I_CURRENT_THREAD to be set to NULL during exit, which causes the
segfault, but this only happens with guile-1.8.8 (haven't checked
earlier releases).