From: Sean Doran <smd@ebone.net>
Subject: Re: make of qgnus-0.11 hangs formatting info files
Date: 29 Sep 1997 21:43:20 +0200 [thread overview]
Message-ID: <52afgvkisn.fsf@sean.ebone.net> (raw)
In-Reply-To: Stainless Steel Rat's message of "29 Sep 1997 14:10:19 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> SD> "GNU Emacs 20.2.2 (i386-unknown-netbsd1.2G, X toolkit)
> ^^
> That could be the problem. It makes just fine with
> 19.34.
Nope, it's architechture-dependent, since a build on a
NetBSD SPARC with the same compiler options, with the
compiler (and everything else) built from roughly the same
SUPped sources works just fine.
BTW, this is the first lossage I've seen with emacs-20.2
with the MBSK.
I'm fiddling with compiler options. Simple -O didn't work.
I got a mildly interesting stack backtrace by using the
SIGQUIT and if the fiddled compiler options
(force-mem/force-addr) doesn't solve the lossage, and
turning off optimization altogether doesn't either,
then I'll see if I can reproduce it in an interactive
Emacs in which I can toggle debug-on-error to t.
Sean.
next prev parent reply other threads:[~1997-09-29 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-29 17:14 Sean Doran
[not found] ` <x7pvpsyos4.fsf@peorth.gweep.net>
1997-09-29 19:43 ` Sean Doran [this message]
1997-09-29 23:51 ` St. Suika Roberts
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=52afgvkisn.fsf@sean.ebone.net \
--to=smd@ebone.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).