You could just fire up a REPL and do exactly what the snow script does.

(include "/usr/share/snow/base/snow.scm") ; include snow macros (include-cd* "program.scm") ; makes sure includes work the way they should (load-program* "program.scm")

That should throw you into the debugging environment. It looks like snow invokes gambit with the -:d- runtime option, which means it overrides the 'r' option which would start a REPL on error. I think snow should have a '--debug' option which sets these kinds of parameters (I have added it to my version of snow, so it also compiles with the debugging flags).

On 9/8/07, andrew cooke andrew@acooke.org wrote:

Hi,

I'm developing a bunch of packages using Snow and Gambit and really need some help with debugging. I am using generic Snow scripts as defined in the documentation.

Is there some way of using an interactive prompt (at this point I have quite a lot of interdependent packages if that makes any difference)?

Alternatively, is there some way to enable stack traces? Or anything similar?

For example, at the moment I see:

qp6 lines: SNOW_TEST="lines-base" ./lines-base.scm *** ERROR IN #<procedure #2>, "../../../pkg/gambc-4.0b22/4.0b22/syntax-case.scm"@9169.1 -- no expressions in body (lambda (#(#(source1) first "/home/andrew/projects/personal/src/scheme/lines...

and I have no idea what part of my code that might be related to.

I probably just need to be pointed at the appropriate documentation - I looked on the Snow site, but it seems to imply that I need to read a Gambit-specific section that doesn't exist(?).

Thanks! Andrew

---

Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list