unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Kevin H <kevin.l.holmes@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: variable-ref segfaults regular variables
Date: Thu, 27 Jan 2011 10:50:36 +0100	[thread overview]
Message-ID: <m3sjweisk3.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTimqHO_qzvRM8WJzE00rD0eMW=ecJdWAaOqrwX6Q@mail.gmail.com> (Kevin H.'s message of "Mon, 24 Jan 2011 15:44:32 -0500")

Hi Kevin,

On Mon 24 Jan 2011 21:44, Kevin H <kevin.l.holmes@gmail.com> writes:

> (define x 42)
>
> (variable-ref x)
>
> I get a segmentation fault every time.

Fixed in git.  Thanks for the report!

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2011-01-27  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 20:44 variable-ref segfaults regular variables Kevin H
2011-01-27  9:50 ` Andy Wingo [this message]

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=m3sjweisk3.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=kevin.l.holmes@gmail.com \
    /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).