From: Andreas Rottmann <a.rottmann@gmx.at>
Subject: Re: Segfault using call/cc on ia64 (and possibly others)
Date: Sat, 22 Jan 2005 02:46:35 +0100 [thread overview]
Message-ID: <87brbijkw4.fsf__10407.719834666$1117217387$gmane$org@ivanova.rotty.yi.org> (raw)
In-Reply-To: <87hdlae860.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 22 Jan 2005 09:20:23 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Andreas Rottmann <a.rottmann@gmx.at> writes:
>>
>> Segfaults in the G-Wrap testsuite[0] seem to indicate that this might
>> be a problem on alpha,
>
> Your one-liner seems ok for me on alpha. Propose something for the
> test suite in any case.
>
This means I'm going to have to investigate this G-Wrap testsuite
segfaults further on at least alpha and sparc.
Regards, Rotty
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2005-01-22 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <873bwulq83.fsf@ivanova.rotty.yi.org>
2005-01-21 22:20 ` Segfault using call/cc on ia64 (and possibly others) Kevin Ryde
[not found] ` <87hdlae860.fsf@zip.com.au>
2005-01-22 1:46 ` Andreas Rottmann [this message]
2005-01-21 16:08 Andreas Rottmann
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='87brbijkw4.fsf__10407.719834666$1117217387$gmane$org@ivanova.rotty.yi.org' \
--to=a.rottmann@gmx.at \
/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).