unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: simple-format causes segfault?
Date: Sun, 07 May 2006 00:20:45 +0100	[thread overview]
Message-ID: <877j4yrb8y.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <20060506033853.GB26686@aphex.iro.umontreal.ca> (James Bergstra's message of "Fri, 5 May 2006 23:38:54 -0400")

James Bergstra <james.bergstra@umontreal.ca> writes:

> Hi,
>
> I'd like to file a bug report on guile-1.8, but I don't know how.

You're already doing the right thing: writing to bug-guile@gnu.org.

> I have a program that causes the guile interpreter to segfault when I output
> with (simple-format), but runs properly when I replace the simple-format with
> what I believe are equivalent calls to (display).
>
> I'd like to file a bug-report. Should I
> a) attach cores
> b) attach cores + program text
> c) attach cores + program text + data files
> d) do nothing, because this another known issue 
>    (is there a list of known issues?)

To begin with, please just post the code and any input that it needs
to repro the problem.  That should be enough if the problem is not
specific to your environment.  If it isn't enough, we can move onto
cores later.

Thanks,
        Neil 



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


  parent reply	other threads:[~2006-05-06 23:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06  3:38 simple-format causes segfault? James Bergstra
2006-05-06 22:39 ` Marius Vollmer
2006-05-06 23:20 ` Neil Jerram [this message]
2006-05-07 18:15   ` James Bergstra
2006-05-07 23:12     ` Kevin Ryde
2006-05-09  0:58     ` Rob Browning
2006-05-09  2:35       ` Rob Browning

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=877j4yrb8y.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).