From: David Fang <fang@csl.cornell.edu>
To: 15750@debbugs.gnu.org
Subject: bug#15750: Acknowledgement (segfault during snarf-check-and-output-texi on x86_64-darwin11 (guile-2.0.9))
Date: Wed, 30 Oct 2013 19:17:01 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1310301915520.19528@hal-00.csl.cornell.edu> (raw)
In-Reply-To: <handler.15750.B.138308231515650.ack@debbugs.gnu.org>
On x86_64-darwin11 (clang-built, -g -O2), the exit status of the failure
is not even consistent from run-to-run, nondeterministic behaviour!
example log:
http://paste.lisp.org/display/139704#8
Fang
next prev parent reply other threads:[~2013-10-30 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 21:31 bug#15750: segfault during snarf-check-and-output-texi on x86_64-darwin11 (guile-2.0.9) David Fang
[not found] ` <handler.15750.B.138308231515650.ack@debbugs.gnu.org>
2013-10-29 23:15 ` bug#15750: Acknowledgement (segfault during snarf-check-and-output-texi on x86_64-darwin11 (guile-2.0.9)) David Fang
2013-10-30 23:17 ` David Fang [this message]
2013-11-01 18:37 ` David Fang
2013-11-01 19:51 ` bug#15750: Closing this bug Mark H Weaver
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=Pine.LNX.4.64.1310301915520.19528@hal-00.csl.cornell.edu \
--to=fang@csl.cornell.edu \
--cc=15750@debbugs.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).