From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Odd error after CVS build
Date: Fri, 13 Feb 2004 12:33:44 -0500 [thread overview]
Message-ID: <E1ArhCC-0007Ys-RC@fencepost.gnu.org> (raw)
In-Reply-To: <16426.41092.881843.187716@magrathea.basistech.com> (message from Tom Emerson on Wed, 11 Feb 2004 16:37:07 -0500)
> That message comes from Flread. How about making a backtrace, then
> stepping thru to see what causes the problem?
If I invoke emacs with --debug-init then I get the error when the
debugger tries to load...
We're talking about C code, so you need to use GDB, not the Lisp
debugger. Please put a breakpoint into Fload using GDB and make a
backtrace from there.
prev parent reply other threads:[~2004-02-13 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 17:49 Odd error after CVS build Tom Emerson
2004-02-11 14:58 ` Richard Stallman
2004-02-11 21:37 ` Tom Emerson
2004-02-13 17:33 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1ArhCC-0007Ys-RC@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).