From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: Segment fault when Guile displays a backtrace
Date: Wed, 25 Jul 2007 01:25:06 +0200 [thread overview]
Message-ID: <87sl7dfkq5.fsf@chbouib.org> (raw)
In-Reply-To: 595e78020707011913x2aaf3fc8le0bcc74b1eafcf32@mail.gmail.com
Hi,
xeos <xeos00@gmail.com> writes:
> 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)
"Luigi Semenzato" <luigi@semenzato.com> writes:
> $ guile
> guile> (version)
> "1.8.1"
> guile> (set! 'x #t)
>
> Backtrace:
> In standard input:
> 2: 0* Segmentation fault (core dumped)
I fixed it in CVS, so it will be in the next stable release.
Thanks,
Ludovic.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2007-07-24 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 2:13 Segment fault when Guile displays a backtrace xeos
2007-07-10 21:31 ` Ludovic Courtès
2007-07-24 23:25 ` Ludovic Courtès [this message]
-- 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=87sl7dfkq5.fsf@chbouib.org \
--to=ludo@gnu.org \
--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).