From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Building Go/386
Date: Sat, 31 Aug 2013 19:09:57 +0200 [thread overview]
Message-ID: <933b46f22d6c3cf1b6b7787b8269d4c8@proxima.alt.za> (raw)
In-Reply-To: <399e128253888fad1131901a3e8b6672@kw.quanstro.net>
> since even ghostscript doesn't get into this state, i'd be interested
> in the line of code (and types of the variables) that hits this fatal
> condition.
I'll see if I can track down more details, I'm relieved there are
others out there who can fathom out these situations (and show some
concern)...
++L
next prev parent reply other threads:[~2013-08-31 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 14:36 lucio
2013-08-31 15:11 ` erik quanstrom
2013-08-31 17:09 ` lucio [this message]
2013-08-31 18:12 ` lucio
2013-08-31 21:16 ` erik quanstrom
2013-09-02 18:15 ` Nick Owens
2013-09-02 20:50 ` Rob Pike
2013-09-02 21:51 ` erik quanstrom
2013-09-02 22:08 ` Nick Owens
2013-09-03 0:28 ` erik quanstrom
2013-09-04 6:07 ` lucio
2013-09-07 11:19 ` Anthony Martin
2013-09-07 13:07 ` erik quanstrom
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=933b46f22d6c3cf1b6b7787b8269d4c8@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).