From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Compile failure on IRIX 6.5
Date: Wed, 23 Feb 2005 15:37:30 -0500 [thread overview]
Message-ID: <E1D43GE-0002lH-AC@fencepost.gnu.org> (raw)
In-Reply-To: <20050223103642.3e1339cd.daichi.k@dance.ocn.ne.jp> (message from Daichi Kawahata on Wed, 23 Feb 2005 10:36:42 +0900)
You must not expect us to intuit where the cause of this bug is. That
is very hard. If you want to fix this bug, you will have to debug it.
Nobody else can debug it, unless he can make it fail.
You may as well start by reading lisp.h and learning the format of
Lisp objects, so that you can figure out what each object mean.
I'm afraid I have no idea what can be considered stack overflow.
Look at the stack pointer; you'll have to learn about the machine's
conventions to see what's a valid stack pointer value.
(dbx) p Vprint_length
272150529
What does that number mean as a Lisp Object on your platform?
Is it nil? Look in Qnil and see what you find.
> The question is, why is that happening? The crucial point for
> finding the Emacs bug is, what Lisp program is trying to print
> something,
Does that mean built-in/included Lisp program? as a total beginner,
I'd think option '-q' has Emacs not to take any initial/external
file.
The task at hand is to find out what's happening.
Lisp code is being run. What code, and why?
prev parent reply other threads:[~2005-02-23 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 17:59 Compile failure on IRIX 6.5 Daichi Kawahata
2005-02-21 10:21 ` Richard Stallman
2005-02-23 1:36 ` Daichi Kawahata
2005-02-23 20:37 ` Richard Stallman [this message]
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=E1D43GE-0002lH-AC@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.