Hi everyone,
I have found a bug on cvs guile. It has been reproduced by two users
more too. When Guile crashed when it evaluates a wrong expression of
the form:
(set! 'symbol value)
Guile should throw (and it do throw) a exeption, Nevertheless it
crashed in the middle of backtrace log. Excuse me. I would have like
send a patch in order to fix it but but I am not familiarized with
guile project. Anyway, I put output of gdb below.
It is the output log:
$ guile
guile> (set! 'symbol value)
Backtrace:
In standard input:
1: 0* Violación de segmento
and it is the gdb output log:
[Thread debugging using libthread_db enabled]
[New Thread -1211996480 (LWP 12319)]
[New Thread -1214342256 (LWP 12322)]
guile> (set! 'd 5)
Backtrace:
In standard input:
1: 0*
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1211996480 (LWP 12319)]
unmemoize_exprs (exprs=0xb7b7ab30, env=0xb7b7aba0) at eval.c:588
588 {
(gdb) backtrace
#0 unmemoize_exprs (exprs=0xb7b7ab30, env=0xb7b7aba0) at eval.c:588
#1 0xb7e730b8 in unmemoize_expression (expr=0xb7b7ab80, env=0xb7b7aba0)
at eval.c:955
#2 0xb7e73245 in unmemoize_exprs (exprs=<value optimized out>,
env=0xb7b7aba0)
at eval.c:613
#3 0xb7e730b8 in unmemoize_expression (expr=0xb7b7ab80, env=0xb7b7aba0)
at eval.c:955
#4 0xb7e73245 in unmemoize_exprs (exprs=<value optimized out>,
env=0xb7b7aba0)
at eval.c:613
#5 0xb7e730b8 in unmemoize_expression (expr=0xb7b7ab80, env=0xb7b7aba0)
Good luck and excuse me again. :-)
--
Is all that we see or seem but a dream within a dream?
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
