From: xeos <xeos00@gmail.com>
To: bug-guile@gnu.org
Subject: Segment fault when Guile displays a backtrace
Date: Mon, 2 Jul 2007 04:13:12 +0200 [thread overview]
Message-ID: <595e78020707011913x2aaf3fc8le0bcc74b1eafcf32@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1745 bytes --]
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?
[-- Attachment #1.2: Type: text/html, Size: 2479 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2007-07-02 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 2:13 xeos [this message]
2007-07-10 21:31 ` Segment fault when Guile displays a backtrace Ludovic Courtès
2007-07-24 23:25 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2007-07-02 13:15 Marco Maggi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=595e78020707011913x2aaf3fc8le0bcc74b1eafcf32@mail.gmail.com \
--to=xeos00@gmail.com \
--cc=bug-guile@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).