(project all) is a module that loads all of the prerequisites and submodules (about 4k lines total) and exports symbols. These steps happen in the directory 'project' containing '
main.scm' and 'foo.scm'.
I have two questions. Is there something intrinsically wrong with with setting the current module to the one on which I am actively working and then just reloading that file rather than the entire suite? (
I.e., there are usually a lot of testing steps between the 'set-current-module' form and the 'load' form; however, the steps above will always produce a crash.)
My second question is this: given that the answer to 1) is no, how do I track this pest down? Placing an undefined identifier, say 'x', at various points in one of the modules will sometimes produce the appropriate warning, sometimes produce a segfault, other times a bus error or illegal instruction or even an abort during gc. I have run attached to gdb, but I get a deep stack (131 frames) ending with,
#0 scm_gc_sweep () at ../../../src/guile-1.6.8/libguile/gc.c:1729 #1 0x0021f573 in scm_igc (what=0x26c720 "cells") at ../../../src/guile-1.6.8/libguile/gc.c:1161 #2 0x0021fa83 in scm_gc_for_newcell (master=0x273440, freelist=0x273438) at ../../../src/guile-
1.6.8/libguile/gc.c:985 #3 0x00238aef in scm_cons (x=0x6826c0, y=0x2974) at ../../../src/guile-1.6.8/libguile/pairs.c:84 #4 0x00216b87 in scm_deval (x=0xc3028, env=0x682480) at ../../../src/guile-1.6.8/libguile/eval.c:2835
#5 0x00219af5 in scm_deval (x=0xc3030, env=0x682480) at ../../../src/guile-1.6.8/libguile/eval.c:2819