RE: set-current-module in .guile ?

["Walck, Scott" <walck@lvc.edu>]

Hi,

I don't think it's the + function.  I get a segfault just by typing (exit).  I don't get a core file, though, in either case.  Why is that?

scott@dell:~/computer/guile$ guile
guile> (load "/usr/local/src/guile-scmutils/src/load.scm")
guile> (module-use! (current-module) generic-environment)
#f
guile> (exit)
Segmentation fault (core dumped)

Thanks,

Scott


________________________________________
From: guile-user-bounces+walck=lvc.edu@gnu.org [guile-user-bounces+walck=lvc.edu@gnu.org] On Behalf Of Ludovic Courtès [ludo@gnu.org]
Sent: Monday, April 07, 2008 3:16 AM
To: guile-user@gnu.org
Subject: Re: set-current-module in .guile ?

Hi,

"Walck, Scott" <walck@lvc.edu> writes:

> guile> (+ (vector 5 6) (vector 7 8))
> Segmentation fault (core dumped)

It's possible that it's a bug in your implementation of `+', i.e., in
`guile-scmutils'.  Can you run gdb on the core (using "gdb `which guile`
core") and show us the backtrace (using "bt" within gdb)?

> guile> (set-current-module generic-environment)
> #<directory (guile-user) b7bd75e0>
> guile> +
> #<procedure g:+ args>
> guile> (+ (vector 2 3) (vector 5 6))
> #(7 9)

Strange that it works here.  So the above segfault may not be due to
`guile-scmutils'...

Thanks,
Ludovic.