From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Compile failure on IRIX 6.5 Date: Wed, 23 Feb 2005 15:37:30 -0500 Message-ID: References: <20050221025912.08f3701a.daichi.k@dance.ocn.ne.jp> <20050223103642.3e1339cd.daichi.k@dance.ocn.ne.jp> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1109191299 8045 80.91.229.2 (23 Feb 2005 20:41:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 23 Feb 2005 20:41:39 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 23 21:41:37 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D43Hm-0004SM-57 for ged-emacs-devel@m.gmane.org; Wed, 23 Feb 2005 21:39:06 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D43ZB-0006Sb-Su for ged-emacs-devel@m.gmane.org; Wed, 23 Feb 2005 15:57:05 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D43XG-0005rk-EU for emacs-devel@gnu.org; Wed, 23 Feb 2005 15:55:06 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D43XA-0005o5-1G for emacs-devel@gnu.org; Wed, 23 Feb 2005 15:55:00 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D43X9-0005mV-T6 for emacs-devel@gnu.org; Wed, 23 Feb 2005 15:54:59 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D43GE-0002DK-JN for emacs-devel@gnu.org; Wed, 23 Feb 2005 15:37:30 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1D43GE-0002lH-AC; Wed, 23 Feb 2005 15:37:30 -0500 Original-To: Daichi Kawahata In-reply-to: <20050223103642.3e1339cd.daichi.k@dance.ocn.ne.jp> (message from Daichi Kawahata on Wed, 23 Feb 2005 10:36:42 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33766 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33766 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?