From: Ross Boylan <ross@biostat.ucsf.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: debugging load failure [vanished?]
Date: Sat, 14 Sep 2013 16:13:52 -0700 [thread overview]
Message-ID: <1379200432.16341.161.camel@localhost> (raw)
In-Reply-To: <1379188812.16341.151.camel@localhost>
The loading seems to be successful now, even though I haven't changed
anything--except that I did edit ess-site.el, adding and then removing
(edebug).
Could there have been some compiled version that got cleared out by
that process?
Some more details on the failure I was experiencing below.
On Sat, 2013-09-14 at 13:00 -0700, Ross Boylan wrote:
> I am new to debugging elisp.
>
> My .emacs file includes (load "ess-site"). This used to work, but no
> longer seems effective--there is no sign that ESS has been loaded.
> There is also no error, and nothing in *Messages* indicating a problem.
> Other code in .emacs is being evaluated.
Eli wrote:
> So why do you think ess-site is not loaded. All the signs you
> mentioned say otherwise.
>
> You can put
>
> (message "ess-site start")
>
> at the beginning of your ess-site.el, and see if that message gets
> displayed and logged in the *Messages* buffer.
>
I say the load was ineffective because
1) M-x ess <complete> doesn't get anything
2) M-x r is an unknown command
3) There is no *ESS* buffer
More recently it has been clear that ess-site.el was loading, because
when I put (edebug) in it a debugger came up.
Ross
>
> emacs --debug-init doesn't help (that is, emacs launches the same way it
> does without the option), presumably because there is no error.
>
> I would like to trace through and see what's going on.
>
> With the cursor inside (load "ess-site") M-x edebug-eval-top-level-form
> starts the debugger. I then hit "i", which I think is the way to step
> into the lower level evaluations.
>
> This asks for a C source file (apparently the load is defined internally
> in C) which a) is not on my system; b) doesn't seem as if it would be
> meaningful to an elisp debugger; and c) is not likely to be where the
> problem lies. I really want to see the code in ess-site. At any rate,
> I can't get past this step.
>
> How can I get my hands on something to debug?
>
> I do have the ess-site.el, and tried putting (edebug) inside of it. I
> think this brought up the regular debugger (since it was not edebug
> instrumented), but it didn't show me where I was in the source and I
> couldn't do anything useful. (It also show the load command is loading
> the file). Probably a more experienced person could do something
> useful, but I could use some help. I think I want to use edebug not
> debug since the former is friendlier.
>
> Running emacs 23.4.1 on Debian GNU/Linux (wheezy).
>
> Thanks.
> Ross Boylan
>
> P.S. I would appreciate a cc on the response.
>
prev parent reply other threads:[~2013-09-14 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 20:00 debugging load failure Ross Boylan
2013-09-14 20:59 ` Eli Zaretskii
2013-09-14 23:13 ` Ross Boylan [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=1379200432.16341.161.camel@localhost \
--to=ross@biostat.ucsf.edu \
--cc=help-gnu-emacs@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.
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).