From: "Drew Adams" <drew.adams@oracle.com>
To: "'Larry Evans'" <cppljevans@suddenlink.net>, <help-gnu-emacs@gnu.org>
Subject: RE: (debug) backtrace: how to show source code at current location.
Date: Wed, 5 Jan 2011 11:06:59 -0800 [thread overview]
Message-ID: <4678E0C82C5D4DAB81AF90DFA7E07027@us.oracle.com> (raw)
In-Reply-To: <ig2c21$vqb$1@dough.gmane.org>
> Please, how can I find out what's causing this error message:
>
> "(wrong-type-argument arrayp tab)"
From your error message alone, it seems that the symbol `tab' is being passed to
some function that expects an array. That's not much help yet, but things might
become clearer when you dig deeper using the debugger.
(setq debug-on-error t)
1. Load source (*.el) files for the library where the error occurred.
IOW, look at the `debug-on-error' backtrace to see which function(s) were
involved when the error occurred. Then use `C-h f' or `find-func' to find the
function definition(s) (source file(s)). Load the source file(s) (*.el) using
`load-file' or `load-library', including the extension `.el' in the name.
2. Provoke the error and backtrace again. It should now show more source-code
entry points instead of byte-code (the `(byte-code "ÁÂÃ...' stuff)
3. You can also use `M-x debug-on-entry THE-FUNCTION' to enter the debugger
whenever a problematic function is invoked. Then you can walk through the
invocation to see more about what caused the error.
next prev parent reply other threads:[~2011-01-05 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 18:07 (debug) backtrace: how to show source code at current location Larry Evans
2011-01-05 19:06 ` Drew Adams [this message]
2011-01-05 19:43 ` Larry Evans
2011-01-05 19:54 ` Larry Evans
2011-01-05 19:58 ` Drew Adams
[not found] ` <mailman.0.1294256637.13904.help-gnu-emacs@gnu.org>
2011-01-05 23:31 ` Tim X
2011-01-06 2:53 ` Larry Evans
2011-01-06 3:50 ` Larry Evans
2011-01-06 3:55 ` Drew Adams
2011-01-06 4:50 ` Larry Evans
2011-01-06 13:57 ` Drew Adams
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=4678E0C82C5D4DAB81AF90DFA7E07027@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=cppljevans@suddenlink.net \
--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).